Execution, delegation, and tracking

executeIntent, walletExecute, delegation tools, agentWalletBootstrap, and post-trade analytics.

Execution tools submit catalog-backed intents. Unsupported actions are rejected before broadcast.

Write rails

Tool	When
`walletExecute`	Single agent-owned execution wallet (`runMode=agent_wallet`) after `agentWalletBootstrap`
`executeIntent`	Fan-out / subscriber lane, hybrid and thirdfy delegated users
`agentRun`	Higher-level run wrapper with JSON params (common in MCP hosts)
`buildTx`	BYOW unsigned tx preparation (`runMode=self`)
`walletSign` + `walletSubmit`	BYOW sign and broadcast
`getIntentStatus`	Poll execute-intent fanout jobs only

For walletExecute, read txHash, blockedReason, and blockedStage from the direct response. Do not poll getIntentStatus for solo wallet executes.

Recommended write sequence

Onboarding (once): Onboarding tools
getActionsCatalog
getAgentActions
getProviderActions for the venue family
getChainCapabilities or getNonEvmCapabilities
Readiness gate
- agent_wallet: agentWalletBootstrap with requireFundingCheck: true when collateral is required
- self: getSelfReadiness then buildTx / walletSign
- hybrid / thirdfy: delegationStatus and active Gator binding
Write via the rail that matches runMode
Analytics: trackAgentAction and portfolio reads (see Tracking below)

Run mode quick reference

Mode	Authority	Typical MCP path
`agent_wallet`	Managed execution wallet	`agentWalletBootstrap` → `walletExecute`
`thirdfy` / `hybrid`	Delegated user wallet	`delegation*` → `executeIntent` or `agentRun`
`self`	Local signer	`buildTx` → `walletSign` → `walletSubmit`

Off-chain venue orders (Hyperliquid, Polymarket CLOB, Bitfinex) use venue credentials or managed wallets. Do not use self for those order paths.

Delegation tools manage Gator / ERC-7710 authority for thirdfy and hybrid lanes. Managed wallet tools set up custodial delegation wallets. agentWalletBootstrap resolves the solo execution wallet for agent_wallet.

Delegation tools

Tool	Purpose
`delegationCreate`	Start Gator delegation binding
`delegationActivate`	Activate after external signature
`delegationStatus`	Current binding state
`delegationInspect`	Deep inspect caveats and scopes
`delegationBalance`	Delegated balance reads
`delegationRevoke`	Revoke active delegation
`delegationRedeem`	Convenience helper over `executeIntent` for supported redeem flows

For policy boundaries and MetaMask Gator context, see Delegation and protection and Delegation API.

Managed wallet tools

Tool	Purpose
`managedWalletInit`	Initialize custodial delegation wallet setup
`managedWalletGrant`	Grant access for managed wallet lane
`managedWalletStatus`	Read setup status

Use these only when the product path requires user custodial delegation wallets, not for default solo Hyperliquid or Polymarket agent wallets.

agentWalletBootstrap

Resolves the agent-owned Privy execution wallet at /api/v1/agent/execution-wallet with runMode=agent_wallet.

Fund the returned execution wallet, not the owner embedded login wallet.
For Hyperliquid Bridge2, Bridge2 credits the transaction sender on Arbitrum.
Call with requireFundingCheck: true before first walletExecute when collateral is required.

Hyperliquid and Polymarket solo lanes sign through the managed execution wallet. Do not put venue private keys on the runtime.

Lane selection

Lane	MCP setup	Writes
`agent_wallet`	`agentWalletBootstrap`	`walletExecute`, `agentRun`
`hybrid` / `thirdfy`	`delegationCreate` → `delegationActivate`	`executeIntent`, `agentRun`, `delegationRedeem`
`self`	`getSelfReadiness`	`buildTx`, `walletSign`, `walletSubmit`

Tracking and analytics

Tracking tools record agent observations and read Thirdfy API accounting. They do not bypass execution policy.

Track tools

Tool	Purpose
`trackAgentAction`	Record an action observation (permissive; custom names stored for later catalog review)
`getAgentTrackActions`	List tracked actions for an agent
`getAgentTrackEvents`	Event stream for analytics
`getAgentDataSummary`	Aggregated agent data summary

Execution remains fail-closed through the supported action catalog. Tracking is intentionally permissive so MCP-native agents can log intent before full catalog coverage.

Portfolio and leaderboard

Tool	Purpose
`getAgentPortfolioSummary`	Latest USD principal, NAV, PnL, ROI, APR, holdings, valuation source
`getAgentLeaderboard`	Rank agents by `trading`, `yield`, or `prediction` over `24h`, `7d`, `30d`, or `all`

The MCP does not compute portfolio math locally. Thirdfy API owns principal, valuation snapshots, and leaderboard scoring.

Typical post-trade flow

walletExecute or executeIntent
  → trackAgentAction
  → getAgentPortfolioSummary

Workflow examples

Goal	Discovery	Execute
Spot swap	`getProviderActions { provider: "trading" }`	`walletExecute` or `executeIntent` with `action=swap`
HL perps	`provider: "hyperliquid"`	Setup actions → orders with `agent_wallet` or delegated lane
Polymarket	`provider: "polymarket"`	Funding/setup status → CLOB orders (EU egress for live orders)
Earn deposit	`provider: "earn"` or `morpho` / `aegis`	`deposit_*` actions with correct decimals
Bitfinex funding	`provider: "bitfinex"`	`executeIntent` with `cexCredentialRef`

Venue operator detail lives on Integrations pages and in getProviderActions hints.

Hosted runtime context

Pass optional executionContext (runtimeId, orgId) on walletExecute, executeIntent, and agentRun so Thirdfy credits attribute to the correct EarnClaw or Claude runtime.

MCP discovery tools

getActionsCatalog, getProviderActions, getAgentActions, chain capabilities, and MCP resources.

MCP onboarding tools

Email OTP onboarding, optional agentRegister, bootstrapSelfIdentity, and getSelfReadiness.