Execute Intents

Thirdfy validates and executes intents for registered agents. Any DeFi agent can be validated here.

What is Execute Intent?

Thirdfy is the platform that validates and executes intents for registered agents. Any DeFi agent can be validated here.

  • The agent submits an action (for example a swap, earn deposit, or perps order).
  • Thirdfy validates policy, limits, and allowed actions.
  • Thirdfy builds one execution per delegated user. A delegated executor runs it within that user's delegation scope.
  • One intent produces many executions (async).

Two Execution Models

Thirdfy offers two ways for agents to execute actions:

ModelAPIWho constructsWho signs & broadcastsFlow
Execute IntentPOST /api/v1/agent/execute-intentThirdfy (on our platform)A delegated executor, within each user's delegationAgent submits → Thirdfy validates → fans out to users → one execution per user
Build TxPOST /api/v1/agent/build-txThirdfyAgent or userAgent requests tx → Thirdfy validates & builds unsigned tx → agent/user signs & broadcasts

Execute Intent: Thirdfy orchestrates the full flow. The agent submits one intent. Thirdfy validates it, builds one execution per delegated user, and runs each one within that user's delegation. Capital moves only from that user's wallet, and only inside the user's mandate. Use this when you want Thirdfy to handle fan-out to delegated users.

Build Tx: Thirdfy validates and constructs a single unsigned transaction, then returns it to the agent. The agent or user signs and broadcasts. Thirdfy does not orchestrate execution. Use this when the agent needs to execute for a specific wallet.

What fails on-chain vs off-chain?

Failure pointWhereResult
Policy / mandate violationOff-chain (Thirdfy)Intent rejected before any tx is built
Action not in allowlistOff-chain (Thirdfy)Intent rejected
Invalid params, slippageOff-chain (Thirdfy) or on-chainRejected at validation, or tx reverts on-chain
User revokes before executionOff-chainPending executions cancelled; see Delegation and protection
Tx revert (e.g. insufficient liquidity)On-chainUser's tx fails; no funds moved

Flow

Example: an approved trading agent submits a swap for its delegated users.

Agent: "Swap 10 USDC to the selected token"
         │
         ▼
   Thirdfy validates
         │
         ├── Compliant? ──► Fan out to User 1, User 2, ... User 1000
         │                        │
         │                        ▼
         │                  One execution per user (1,000 swaps)
         │
         └── Rejected? ──► No user receives the intent

Each of the 1,000 executions is checked on its own against that user's delegation and balance.

Security & How We Protect Users

  • Intent-based security: We verify what actions are allowed, not just who holds keys. Thirdfy inserts a runtime policy enforcement layer between agents and financial infrastructure.
  • Full details: See Delegation and protection for delegation modes and best practices.
  • Every intent validated before execution: Policy engine evaluates against mandate and policy. Compliant = authorized. Not compliant = rejected.
  • Verifiable enforcement records: Every authorization decision produces a traceable event.
  • Mandates: Programmable policies for capital allocation, counterparties, timing, and execution parameters. See Delegation and protection.

Execution lanes

Every intent runs in one lane (runMode):

LaneMeaning
thirdfy / hybridDelegated user capital with an active Gator or Thirdfy binding. Fan-out uses these lanes.
selfThe user or agent signs with their own keys.
agent_walletThe agent's own execution wallet. No delegated users.
validation_onlyThirdfy validates and runs reads. Writes are blocked.

Non-custodial delegation uses ERC-7710 (Gator). Delegation is scoped and time-limited. Status is tracked as active, expired, or revoked. The policy engine checks every intent against the user's mandate before execution. Older integrations may send x402_custodial; the API treats it as an alias for server-side delegated execution.

Who pays

Delegated users pay for execution through their USD balance or free requests. Their capital moves only after validation. See Credits for Users for the flow. Agents request; Thirdfy validates; delegated users receive execution.

Free-tier note:

  • Users without paid credits can use a shared daily free-request quota (shared with Console chat).
  • The current limit is 20 free requests a day, reset at 00:00 UTC.
  • If a user has no free quota left, fan-out marks that user's result blocked at stage credits. Other users still execute.

For Agent Creators

  1. Start with Agent CLI or MCP (email OTP onboarding)
  2. Discover allowed actions from the catalog
  3. Choose your execution model, then follow that path:
    • Solo agent_wallet (most builders): Preflight, then CLI run --run-mode agent_wallet or MCP walletExecute / agentRun
    • Execute Intent fan-out: Preflight, then CLI run --run-mode thirdfy (or a network profile), MCP executeIntent, or POST /api/v1/agent/execute-intent for delegated subscribers; poll status until complete
    • Build Tx: POST /api/v1/agent/build-tx (or MCP buildTx) for a single unsigned tx, then sign and broadcast locally
  4. Prefer CLI or MCP for day-to-day work. Use the HTTP API when you need a custom backend.

FAQ

Related

Credits
How Thirdfy credits work for people and agents. Free requests each day, how an agent checks its balance, and how to top up with USDC on Base.
Supported chains
Every chain where Thirdfy agents can act today, EVM and Solana, with chain IDs, run modes and venue links.