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.
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.
| Bankr | Thirdfy | |
|---|---|---|
| Operator UI | Terminal | Console |
| CLI | @bankr/cli (bankr agent prompt) | @thirdfy/agent-cli (preflight, run, credits) |
| IDE / managed agents | Claude plugins, Bankr skill | Thirdfy MCP |
| Headless API | Wallet API + Agent API | Execute-intent, build-tx, chat stream |
| Wallet model | Agent wallet provisioned at login | Execution wallet, delegation, and venue credentials |
| Skills | One primary bankr skill + bankr agent skills | Optional thirdfy-skills repo; CLI and MCP are the default rails |
| Automation | Bankr jobs / automations | Console automations + EarnClaw hosted agents |
| Monetization | Club + LLM gateway credits | Credits + 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)
- Sign in at thirdfy.com/console.
- Connect wallet and complete delegation when Command should execute writes.
- Fund balances and complete venue setup (Hyperliquid, Polymarket, Lighter) when needed.
- Use Command or Help Hub example prompts. Execution runs through the same API policy layer as CLI and MCP.
Builders (CLI or MCP)
- CLI:
thirdfy-agent login emailor setAGENT_API_KEYfrom Creator Platform if you prefer the web UI. - MCP: Connect
https://mcp.thirdfy.com/mcpand runstartEmailOnboarding→completeEmailOnboarding. - Discover actions:
thirdfy-agent actions --jsonor MCPgetActionsCatalog. - Preflight, then execute:
thirdfy-agent runor MCPexecuteIntent/walletExecute. - Poll:
thirdfy-agent intent-statusor MCPgetIntentStatus.
Custom backends (HTTP)
GET /api/v1/agent/actions/catalog(no auth).POST /api/v1/agent/execute-intentwith your agent API key.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 browser | Console |
| Running scripts, cron, or Hermes on Fly | Agent CLI |
| Building in Claude, Cursor, or an MCP host | Thirdfy MCP |
| Shipping a custom backend or one-off curl | HTTP API |
| Deploying always-on template agents | EarnClaw |
| Installing instructions into OpenClaw/Hermes skill folders | thirdfy-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
- Console: Operator command center docs
- Build with Thirdfy
- Quick start
- Delegation and protection
- Console early access (operator surface)