OpenAI and ChatGPT-style hosts

Connect Thirdfy MCP from OpenAI-compatible agents — URL, auth, onboarding, and execution.

What you need

  • An MCP-capable host (custom agent, API gateway, or compatible IDE plugin)
  • Email for OTP or an existing Thirdfy agent API key

Install

Point your host at the managed endpoint:

ItemValue
MCP URLhttps://mcp.thirdfy.com/mcp
REST fallbackPOST https://mcp.thirdfy.com/tool/<toolName>
ManifestGET https://mcp.thirdfy.com/tools

If your host supports headers, set Authorization: Bearer <THIRDFY_API_KEY> for credentialed edge auth. Tool bodies still need agentApiKey for walletExecute and related writes.

Verify connection

curl -s https://mcp.thirdfy.com/health
curl -s -X POST https://mcp.thirdfy.com/tool/getActionsCatalog \
  -H "Content-Type: application/json" -d '{}'

Create account and wallets

Call in order (REST or MCP):

  1. describeOnboardingPath
  2. startEmailOnboarding
  3. completeEmailOnboarding with OTP and acceptTerms: true
  4. getWalletProfile
  5. agentWalletBootstrap

Persist the agent API key from the complete response.

First reads

getActionsCatalog → getProviderActions → getVenueReadiness

Use provider or providerId on provider discovery.

Writes

Complete venue onboarding when readiness shows blockers, then walletExecute or agentRun. Omit userDid when agentKey is a 0x address.

Troubleshooting

IssueFix
401 on edgeAdd Bearer token or use anonymous-safe tools only
Schema errorsMatch tool names from GET /tools exactly
Deep nested payloadsPrefer top-level markets / readiness fields on execute responses

Related

MCP client guides
Connect Thirdfy MCP in Cursor, Claude, OpenAI-style hosts, and OpenClaw — email onboarding first, then discovery and writes.
OpenClaw and Hermes
Thirdfy MCP from OpenClaw runtimes — agentApiKey, executionContext, and email onboarding.