Integrations at runtime
How EarnClaw-hosted agents reach every venue and data provider through the Thirdfy action catalog, Agent CLI, and MCP.
When a finance agent runs a live cycle, EarnClaw applies the policy you configured in the wizard before any onchain action executes. You see the outcome in run history: executed intents or a documented skip with a reason code.
Configure delegation and guardrails in Create your first agent. Manage your runtime plan in Settings. See Runtime plans and execution and Fund and run.
One catalog, two surfaces
EarnClaw does not ship a separate integration SDK per venue. Every integration hosted agents use (trading, yield, prediction, bridges, and market data) is exposed through the Thirdfy action catalog. Runtime packs call that catalog through:
| Surface | Used by | Role |
|---|---|---|
| Thirdfy Agent CLI | Hermes and OpenClaw packs | Preflight, catalog discovery, data reads, and execute-intent from hosted adapters and skills |
| Thirdfy MCP | Claude managed agents (and MCP-capable runtimes) | Same catalog and policy surface over streamable HTTP tools |
Whether the agent fetches an Allora forecast, a CoinGecko price, a Vaults.fyi ranking, a Hyperliquid quote, or places a Polymarket order, the path is the same: governed catalog action → preflight when execution is involved → receipt in run history.
Execution volume is included in your EarnClaw runtime plan. You do not set up a separate Thirdfy retail account to deploy on EarnClaw.
What runs on each cycle
| Layer | What it does in EarnClaw |
|---|---|
| Evidence | Template adapters pull venue and market-data context through catalog reads (CLI or MCP) |
| Preflight | Checks the intent against org policy, delegation, template rules, and funding |
| Delegation | Limits what the agent wallet may sign, within scopes and expiry you set |
| Intent execution | Runs approved onchain and tool-backed steps when preflight passes |
| Execution allowance | Meters usage against your runtime plan monthly budget per runtime |
Integration families (all via CLI / MCP)
| Family | Examples in catalog | EarnClaw lanes |
|---|---|---|
| Trading | Kyber spot, Hyperliquid perps, Li.Fi bridge | Trading templates |
| Yield | Vaults.fyi, Yield.xyz, Morpho, Curve | Yield templates |
| Prediction | Polymarket Gamma and CLOB actions | Prediction templates |
| Market data | Allora, CoinGecko, GeckoTerminal, DeFiLlama | Evidence on trading, yield, and prediction packs |
Provider depth, credential models, and operator checklists live in Thirdfy Docs. Market-data reads are covered in Signals and market data.
Thirdfy partnership
EarnClaw partners with Thirdfy for governed execution and the integration catalog. You stay in the EarnClaw workspace. Thirdfy hosts the catalog, preflight, and intent rails your runtime packs call.
| Runtime | How it connects |
|---|---|
| Hermes | EarnClaw-hosted packs call the catalog through the Agent CLI (and API where packs require it) |
| OpenClaw | Gateway and skills call the same catalog through CLI and MCP tools |
| Claude managed | MCP connects managed sessions to catalog discovery, preflight, and wallet execution |
Failed preflight is normal
When policy, funding, delegation, allowance, or venue readiness blocks an action, the agent skips and logs why. That is expected behavior, not a broken agent. Repeated skips with the same reason usually mean a setup gap: wallet funding, expired delegation, plan allowance exhausted, or inactive subscription.
See Observability and Schedules and guardrails.