AI agents: MCP server
A thin directory: one search tool and the agent docs as resources; payment happens on the product URLs.
The MCP server is a directory, nothing more: one tool search (the same GET https://api.awesomefee.com/v1/search?q=) and the agent
docs as resources (llms.txt, SKILL.md, OpenAPI). It does not pay, does not execute and holds no keys. The agent
takes the product URL from search, calls it with its own x402 v2 HTTP client, pays on 402 and gets the result — the
same cycle as without MCP (overview).
Remote
https://api.awesomefee.com/mcp — Streamable HTTP, stateless (no sessions), current MCP revision; 2025-era clients work too.
{ "mcpServers": { "tron-x402": { "type": "http", "url": "https://api.awesomefee.com/mcp" } } }
Local
{ "mcpServers": { "tron-x402": { "command": "npx", "args": ["-y", "tron-x402-mcp"], "env": { "TRON_X402_API_URL": "https://api.awesomefee.com" } } } }
Discovery
https://api.awesomefee.com/.well-known/ai-catalog.json → server card https://api.awesomefee.com/mcp/server-card; x402 manifest https://api.awesomefee.com/.well-known/x402.