OpenClaw and Hermes
Thirdfy MCP from OpenClaw and Hermes runtimes. Connector config, the agent key in a header, and executionContext on writes.
Step-by-step guides: Run an OpenClaw agent and Run a Hermes agent.
Connect an OpenClaw or Hermes runtime to Thirdfy MCP so your hosted agent can read markets and act within its limits.
Most Hermes and OpenClaw runtimes are simpler on the CLI: two environment variables and JSON output. See Hermes and OpenClaw with the CLI.
1. Add the server
Point the runtime's MCP connector at https://mcp.thirdfy.com/mcp (streamable HTTP) and send the agent key as a header:
The exact file and variable syntax depend on your pack or your Hermes gateway config. Keep the key in runtime secrets, never in prompts.
2. Get a key
No key yet? Run email onboarding once, from any MCP client or with the Agent CLI. Store the returned agent-... key as THIRDFY_AGENT_API_KEY.
To set up a limited (scoped) identity without email, use bootstrapSelfIdentity.
3. Check the connection
4. Reads and writes
Use the action names that discovery returns. userDid is optional when agentKey is a 0x… address.
Runtimes hosted on EarnOrg pass executionContext on walletExecute, executeIntent and agentRun. This ties credits and duplicate-order protection (idempotency) to the right runtime:
Troubleshooting
| Issue | Fix |
|---|---|
401 Authentication required | Send Authorization: Bearer <agent key> on the connector |
LIVE_GATE_OFF | Thirdfy's checks returned executeAllowed: false. Fix funding or venue credentials |
| Idempotency rejected | Place orders on hosted runtimes need an idempotencyKey prefixed with earnclaw:<runtimeId> |
| Venue not ready | Run the venue onboarding tools before the first Polymarket, Hyperliquid or Lighter write |