Execute Intent API
Developer API for submitting and tracking agent intents — swap, vote, claim, and more.
Execute Intent API
For AI agents: Use llms.txt for docs discovery, or llms-full.txt for the full API spec in one file (Execute Intent + x402). Read one first.
Submit and track intents for registered agents. Use this API to integrate your AI agent with Thirdfy's Execute Intent platform.
Authentication: Pass your agentApiKey from Creator Platform → Identity tab. Register and claim your agent first.
Base URL
| Environment | Base URL |
|---|---|
| Production | https://api.thirdfy.com |
| Testnet | https://api-test.thirdfy.com |
Endpoints
GET /api/v1/agent/actions/catalog
List the full action catalog with schema, params, and metadata. No authentication required. Use this for docs, LLMs, and SDK discovery. Always reflects the latest actions.
See Actions Reference for full documentation.
GET /api/v1/agent/actions
List allowed actions for your agent. Use this to discover which actions (swap, vote, claim, etc.) your agent can request. Pass agentApiKey to filter to your agent's allowlist; omit to get all actions.
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
agentApiKey | string | No | Your API key from Creator Platform (omit for full list) |
Example
POST /api/v1/agent/execute-intent
Submit an intent. Thirdfy validates policy, limits, and allowed actions, then fans out to delegated users.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
agentApiKey | string | Yes | Your API key |
action | string | Yes | Action type (e.g. swap, vote, claim) |
params | object | Yes | Action-specific parameters |
chainId | number | Yes | Chain ID (e.g. 8453 for Base) |
estimatedAmountUsd | number | No | Estimated USD value for policy limits |
idempotencyKey | string | No | Unique key to prevent duplicate submissions |
Example: Swap
Success response (HTTP 200)
Poll status until status is completed or failed. Completed response:
Rejection response (HTTP 4xx)
GET /api/v1/agent/execute-intent/status
Poll intent status. Call until status is completed or failed.
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
intentId | string | Yes | Intent ID from execute-intent response |
Example
POST /api/v1/agent/build-tx
Build an unsigned transaction for user to sign locally (Model B, non-custodial flow).
Request body
| Field | Type | Required | Description |
|---|---|---|---|
agentApiKey | string | Yes | Your API key |
action | string | Yes | Action type |
params | object | Yes | Action-specific parameters (may include recipient for swap output) |
chainId | number | Yes | Chain ID |
walletAddress | string | No | Wallet address that will sign (some actions use recipient in params) |
Example
Integration Checklist
1. Register Your Agent
Go to thirdfy.com/creator, connect your wallet, and complete onboarding to receive your API key.
2. Get Allowed Actions
Call GET /api/v1/agent/actions to see which actions your agent can request. Enable actions in Creator Platform if needed.
3. Submit Intents
Call POST /api/v1/agent/execute-intent with valid action, params, and chainId. Include idempotencyKey for idempotent retries.
4. Poll Status
Call GET /api/v1/agent/execute-intent/status?intentId=... until status is completed or failed.
5. Handle Rejections
Check HTTP status and error body. Common causes: invalid API key, action not in allowlist, params mismatch, estimatedAmountUsd exceeds policy limit.
OpenClaw Trading Agent Example
Full flow for building an OpenClaw agent that executes trades via Thirdfy Execute Intent.
1. Prerequisites
- OpenClaw agent runtime
- Creator Platform account with registered agent and API key
- Thirdfy skills installed in your agent
2. Install Thirdfy Skills
Add the Thirdfy Intent API skill to your OpenClaw agent. In Creator Platform or your Skills panel, add:
Or from GitHub: https://github.com/thirdfy/thirdfy-openclaw-skills
The skill provides the curl commands your agent will use via the exec tool.
3. Environment Variables
4. Flow: Agent → Thirdfy Execute Intent
5. Agent Logic (Pseudocode)
Your OpenClaw agent uses the exec tool to run curl. Example flow:
- List allowed actions — Before executing, the agent calls
GET /api/v1/agent/actionsto see which actions (swap, vote, claim) it can request. - Submit intent — When the user asks to swap, the agent builds the JSON body and runs:
- Poll status — The agent polls
GET /api/v1/agent/execute-intent/status?intentId=<id>untilstatusiscompletedorfailed. - Report results — Parse
results[](per-user txHash, success) and inform the user.
6. Model A vs Model B
| Model | Skill | Use Case |
|---|---|---|
| Model A | thirdfy-intent-api | Thirdfy signs and fans out to delegated users. No key custody. |
| Model B | thirdfy-tx-builder | Agent builds unsigned tx, signs locally. For advanced autonomy. |
For most trading agents, Model A (Execute Intent) is recommended — Thirdfy handles validation, policy, and fan-out.
When users delegate via MetaMask (ERC-7710), delegation is scoped and time-limited; users retain key custody and can revoke at any time.
7. Skills Reference
- Thirdfy Intent API Skill — Model A, fan-out
- Thirdfy Tx Builder Skill — Model B, local signing
- Thirdfy Check Market Skill — Read-only market and yield intelligence
Related
- Actions Reference — Full action catalog (schema, params, examples). Always up to date from the API.
- llms.txt — Curated map for docs discovery. llms-full.txt — Full API spec in one file.
- Quickstart — Run your first intent with curl
- Execute Intents — Platform overview and flow
- Creator Platform — Register agents, get API keys
- Troubleshooting — Common errors and fixes