Integration paths

Choose how you connect to Thirdfy. Console for operators, Agent CLI and MCP for builders, HTTP API when you need a custom backend.

Connect to Thirdfy

Thirdfy is a governance layer for finance agents. Every path below calls the same policy, delegation, and action catalog. Pick the surface that matches who is using it.

npm install -g @thirdfy/agent-cli
thirdfy-agent login email you@example.com
thirdfy-agent actions --json

Choose your integration path

Console (operators)

Natural-language command center for humans. Chat, positions, delegations, credits, and automations. No skill install required.

Agent CLI

Scripts, CI, Hermes, and Fly runtimes. login, actions, preflight, run, intent-status, credits.

Thirdfy MCP

Claude, Cursor, and MCP-native hosts. Discovery, preflight, executeIntent, walletExecute, onboarding tools.

HTTP API

Custom backends and curl. Catalog discovery, execute-intent, build-tx, x402 credits. Pair with CLI or MCP for day-to-day agent work.

EarnClaw (hosted agents)

Templates, schedules, and dashboard. EarnClaw hosts the runtime; Thirdfy governs execution on the same catalog.

Skills (optional)

SKILL.md wrappers for Hermes, OpenClaw, and other runtimes that install skills by URL. Not required for Console, CLI, or MCP.

From zero to first execution

Operators (Console)

  1. Sign in at thirdfy.com/console.
  2. Connect wallet and complete delegation when Command should execute writes.
  3. Fund balances and complete venue setup (Hyperliquid, Polymarket, Lighter) when needed.
  4. Use Command or Help Hub example prompts. Execution runs through the same API policy layer as CLI and MCP.

Builders (CLI or MCP)

  1. CLI: thirdfy-agent login email or set AGENT_API_KEY from Creator Platform if you prefer the web UI.
  2. MCP: Connect https://mcp.thirdfy.com/mcp and run startEmailOnboarding → completeEmailOnboarding.
  3. Discover actions: thirdfy-agent actions --json or MCP getActionsCatalog.
  4. Preflight, then execute: thirdfy-agent run or MCP executeIntent / walletExecute.
  5. Poll: thirdfy-agent intent-status or MCP getIntentStatus.

Custom backends (HTTP)

  1. GET /api/v1/agent/actions/catalog (no auth).
  2. POST /api/v1/agent/execute-intent with your agent API key.
  3. GET /api/v1/agent/execute-intent/status?intentId=....

See Execute Intent API and Actions reference.

When to use which

You are…Use
A human operating capital in a browserConsole
Running scripts, cron, or Hermes on FlyAgent CLI
Building in Claude, Cursor, or an MCP hostThirdfy MCP
Shipping a custom backend or one-off curlHTTP API
Deploying always-on template agentsEarnClaw
Installing instructions into OpenClaw/Hermes skill foldersthirdfy-skills (optional)

You do not need OpenClaw skill package uploads to use Console, CLI, or MCP. The Creator Platform four-file package (skill.json, skill.md, heartbeat.md, openapi.json) is only for registered OpenClaw agents that want Thirdfy to host their skill manifest.

Supported venues (execution catalog)

Trading, yield, prediction, bridge, and CEX lanes are exposed as governed actions. Discovery works the same on CLI, MCP, and the public catalog API.

  • Integrations hub
  • Live catalog: GET https://api.thirdfy.com/api/v1/agent/actions/catalog

Related

Help and glossary
Short FAQ and terms for integrating with Thirdfy via Agent CLI or MCP.
Trading integrations
On-chain spot, DEX swaps, and Hyperliquid perps. Discovery via MCP/CLI and execution via Execute Intent or wallet rails.