Integrations and venues

Thirdfy execution venues by category. Trading, Yield, Prediction, and CEX integrations with named operator pages.

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

All named venues

Every catalog-backed partner has a dedicated page. Provider keys match MCP getProviderActions and CLI --provider.

Integration flow

  1. Discover actions from the public catalog (curl below).
  2. Filter by provider with MCP or CLI.
  3. Preflight delegation and venue readiness.
  4. 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)

curl "https://api.thirdfy.com/api/v1/agent/actions/catalog"

No authentication required. Response includes actions[], providerFamilies[], and param schemas.

Step 2 — MCP or CLI discovery

SurfaceCommand / tool
MCPgetProviderActions with provider (see MCP)
CLIthirdfy-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.