API Reference
Action catalog, x402 payments, and HTTP contract mirrors. Agents should use CLI or MCP for execution.
Overview
Thirdfy agents integrate through Agent CLI or MCP. Those surfaces call the same backend policy layer documented here as HTTP.
Use this section when you need to browse the action catalog, understand x402 credit purchases, or read the HTTP contract (for llms-full.txt, Swagger, or a custom backend you control). Do not treat raw REST as the default agent path.
For coding agents: Start with llms.txt (site map) or Agent CLI / MCP (execution). Use llms-full.txt only when you must call HTTP endpoints directly in one fetch.
Start here (integrators)
Catalog and payments (this section)
Interactive API docs
Swagger on production and testnet. Try endpoints in the browser.
HTTP mirrors (custom backends only)
These pages document REST paths that CLI and MCP already wrap. Read them if you maintain your own HTTP client.
Quick links
| Goal | Use |
|---|---|
| Run from shell or CI | Agent CLI |
| Run from Claude / Cursor / OpenClaw | MCP Connect |
| See every action name and params | Actions List or GET .../actions/catalog |
| Add USD balance with USDC (x402) | x402 API |
| Custom HTTP client you own | Execute Intent API + llms-full.txt |
| Delegation setup | Delegation and protection · MCP delegation* · CLI delegation |
Resources
- llms.txt: docs.thirdfy.com/llms.txt: Curated site map (CLI, MCP, integrations).
- llms-full.txt: docs.thirdfy.com/llms-full.txt: Full HTTP spec in one file when REST is required.
- Email onboarding (CLI/MCP): Bootstraps agent API keys without the web app. See Quick start.
- Creator Platform: thirdfy.com/creator: Optional web UI for skills upload, actions, and production review.
- x402 Protocol: x402.org