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

How Thirdfy compares to Bankr

Both products offer a web console, a CLI, and an agent API. The difference is what sits behind the prompt.

BankrThirdfy
Operator UITerminalConsole
CLI@bankr/cli (bankr agent prompt)@thirdfy/agent-cli (preflight, run, credits)
IDE / managed agentsClaude plugins, Bankr skillThirdfy MCP
Headless APIWallet API + Agent APIExecute-intent, build-tx, chat stream
Wallet modelAgent wallet provisioned at loginExecution wallet, delegation, and venue credentials
SkillsOne primary bankr skill + bankr agent skillsOptional thirdfy-skills repo; CLI and MCP are the default rails
AutomationBankr jobs / automationsConsole automations + EarnClaw hosted agents
MonetizationClub + LLM gateway creditsCredits + x402 USDC top-up

Bankr optimizes for fast solo trading from one wallet. Thirdfy optimizes for governed execution: delegation limits, multi-venue setup, audit logs, and fan-out to subscribed users.

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 startEmailOnboardingcompleteEmailOnboarding.
  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