Introduction

Thirdfy Skills library and Actions API for agents to execute on-chain DeFi transactions

Quick Start (TL;DR)

Skills in 30 seconds: Install thirdfy-intent-api to use Thirdfy with OpenClaw. That's the primary skill. Add other skills only when you need them. Query the Actions API to discover supported actions, then use Execute Intents or the Tx Builder to fire transactions. Want to contribute? See Create a New Skill and Integrations.

Skills vs Integrations: Skills = what your agent can do (actions, capabilities). Integrations = external tools (LI.FI, CoinGecko MCP, etc.) and custody modes (MetaMask, x402).

Execution Models (Model A vs Model B)

Thirdfy supports two execution modes:

Model	Flow	Key trait
Model A	Execute Intents — Agent submits intent; Thirdfy validates and fans out to subscribed users	No agent key custody. Users pay for execution.
Model B	Tx Builder — Agent builds unsigned tx; user signs locally	User holds keys. User signs each transaction.

Skills like thirdfy-intent-api use Model A. thirdfy-tx-builder uses Model B. See Integrations for custody modes.

Thirdfy Skills Library

Our skills library makes it easy for any agent to execute on-chain transactions: swaps, gauge deposits, credit purchases, and more. Skills are human-readable docs in the thirdfy-openclaw-skills repo; the source of truth for execution is the backend action_catalog exposed via the Actions API.

Discover Actions via API

The skills library can be queried programmatically. Use the Actions endpoint to list all supported on-chain actions, their parameters, and (when authenticated) which actions your agent is allowed to execute.

Route

GET /api/v1/agent/actions

Query parameters:

agentApiKey (optional): When provided, the response is filtered to only actions allowed for that agent's policy. Without it, the full catalog is returned.

Example

# Full catalog (no auth)
curl "https://api.thirdfy.com/api/v1/agent/actions"

# Agent-scoped (only actions your agent can execute)
curl "https://api.thirdfy.com/api/v1/agent/actions?agentApiKey=YOUR_API_KEY"

Response Shape

Each action in the actions array includes:

Field	Description
`action`	Canonical action name (e.g. `swap`, `gauge-deposit`)
`description`	Human-readable description
`requiredParams`	Array of required parameter names
`paramsSchema`	JSON Schema for parameters
`maxAmountUsd`	Optional USD cap for risk controls
`requiresSubscription`	Whether a subscription is required
`implementation`	Implementation identifier
`allowed`	(When `agentApiKey` provided) Whether this action is in the agent's allowlist

Example snippet:

{
  "actions": [
    {
      "action": "swap",
      "description": "Swap tokens via DEX aggregation",
      "requiredParams": ["tokenIn", "tokenOut", "amountIn"],
      "paramsSchema": { "type": "object", "properties": { ... } },
      "maxAmountUsd": 10000,
      "requiresSubscription": true,
      "allowed": true
    }
  ]
}

Technical Notes

The catalog is loaded from the backend action_catalog table (Supabase). Skills in the GitHub repo are human-readable documentation; the API is the execution source of truth.
Action names support both kebab-case and snake_case aliases for compatibility.
After discovering actions, use Execute Intents (POST /api/v1/agent/execute-intent) for fan-out execution, or Tx Builder (POST /api/v1/agent/build-tx) for agent-signed transactions.

Thirdfy Skills (Default Library)

Skill	Tier	Description
thirdfy-intent-api	Primary	Execute intents via fan-out (Model A), no agent key custody. Install this first.
thirdfy-tx-builder	Optional	Build unsigned txs, sign locally (Model B)
thirdfy-agent-gauges	Optional	Gauge operations and protocol metrics
thirdfy-buy-credits	Optional	Credits and x402 payments
jeff-ceo-chat	Optional	Jeff CEO chat integration

We use thirdfy/agentkit (our fork of Coinbase AgentKit) for execution. Our action catalog is synced from AgentKit providers. All actions are supported in Execute Intents and the Skills library. To add a new action provider (e.g. a new DEX or protocol), submit a PR to thirdfy/agentkit.