Integrations and venues
Thirdfy execution venues by category. Trading, Yield, Prediction, and CEX integrations with named operator pages.
For coding agents: Use llms.txt for doc discovery. The action catalog is the source of truth for what can execute today.
Thirdfy routes agent execution through provider families and named venues. Discovery is fail-closed: only catalog-backed actions execute.
Docs grouped by how agents classify intents. For venue-specific operator notes, see Venues.
Categories
Featured integrations
All named venues
Every catalog-backed partner has a dedicated page. Provider keys match MCP getProviderActions and CLI --provider.
Integration flow
- Discover actions from the public catalog (curl below).
- Filter by provider with MCP or CLI.
- Preflight delegation and venue readiness.
- Execute via CLI, MCP, or REST.
Plan 1–2 hours for a first production path with wallet and venue setup. See Quick start sandbox for a ~10 minute catalog smoke test.
Step 1 — Action catalog (copy-paste)
No authentication required. Response includes actions[], providerFamilies[], and param schemas.
Step 2 — MCP or CLI discovery
| Surface | Command / tool |
|---|---|
| MCP | getProviderActions with provider (see MCP) |
| CLI | thirdfy-agent actions (see Agent CLI) |
Hosted deploy (EarnClaw)
EarnClaw (docs.earnclaw.com) is a separate hosted agent platform. Template deploy docs live there. Use Thirdfy docs here for CLI/MCP integration and venue detail. Pointer: Deploy on EarnClaw.