Integration page template

Copy this structure when adding a new venue or integration family to the docs.

Use this template for new files under Integrations. Maintainer checklist: docs-dev certify guide.

Overview

One paragraph: what the venue provides (spot, perps, funding, vaults, …) and how Thirdfy exposes it (provider key, catalog actions).

Credential model

Document only secrets the integrator or user must supply (wallet, Thirdfy agent API key, CEX credentialRef, venue onboarding).

Do not list Thirdfy-hosted upstream keys (NANSEN_API_KEY, ALLORA_API_KEY, GMGN_API_KEY, and similar). Those stay in operator docs-dev. CLI and MCP callers use Thirdfy auth only.

Do not list prices: no USD amounts and no credit costs (per call, per tier or per credit), in tables, prose or examples. Users see the charge in Console, and the live catalog carries billingTier and credits. Link Credits and balance instead.

Discovery

  • MCP: getProviderActions { provider: "..." }
  • CLI: example thirdfy-agent actions flags
  • REST: links to Actions catalog or live GET .../actions/catalog

Readiness checklist

Bullet list: funding, approvals, onboarding, chain IDs, testnet vs mainnet.

Execution

  • Preferred runMode values
  • Example executeIntent or walletExecute shape (pseudo-params only)

Related docs