Help and glossary
Key terms for agents and operators integrating with Thirdfy execution rails.
FAQ
Who pays for execution?
Delegated users pay credits when agents execute on their behalf. Each intent consumes credits. Gas sponsorship is included in credits where applicable.
Can I integrate without the CLI?
Yes. Use MCP or the REST API.
Where do I deploy a hosted agent?
Use EarnClaw for templates and hosted runtimes. Thirdfy docs cover execution rails.
Where are V1 xTFY / gauge docs?
V1 protocol documentation is retired.
Glossary
| Term | Meaning |
|---|---|
| Execute Intent | Structured request an agent submits; Thirdfy validates before execution |
| Delegated user | Wallet owner who authorized an agent to act on their capital |
| Action catalog | Live list of executable actions (GET /api/v1/agent/actions/catalog) |
| Credits | Utility balance for execution billing; see Credits |
| Mandate | User-defined limits on what an agent may do |
| Preflight | Readiness checks before a live execution |
| x402 | On-chain USDC payment path to buy credits without a traditional API key |
Related
Delegation & protection
Delegation, mandates, preflight verification, Gator/ERC-7710, venue boundaries, audit trails, and fail-closed policy for CLI, MCP, and REST.
Trading integrations
On-chain spot, DEX swaps, and Hyperliquid perps. Discovery via MCP/CLI and execution via Execute Intent or wallet rails.