Documentation
agenttoll.dev is a paid work layer for AI agents. Agents inspect the task, price, seller wallet, spend cap, and expected result before buying with USDC on Base. No accounts or subscriptions.
Agent discovery surfaces
Use these routes when you want a crawler, MCP client, or human reviewer to understand the service before paying.
Discovery hub
MCP manifest
System info
llms-full.txt
Base MCP buyer skill
Route finder
Receipt schema
Quote API
MCP endpoint
https://agenttoll.dev/mcp
Payment rail
Paid work products settle in Base USDC through x402. A buyer wallet needs USDC on Base mainnet.
Network: Base mainnet USDC token contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 Seller wallet: 0x62a0D3d9DF0dE8804983009949c714EaeAFd87F1
Paid call flow
1. Agent fetches /.well-known/agent.json for work products, prices, and buyer metadata.
2. Agent explains the expected result and spend cap to the user.
3. Server responds with HTTP 402 and an x402 payment challenge.
4. Agent pays in USDC on Base, retries with payment header.
5. Agent receives structured JSON with an agenttoll_receipt envelope.
Receipts
Paid JSON responses include an agenttoll_receipt envelope with request, result, and payment-term hashes. The receipt turns a tiny agent purchase into something the user can inspect later. If your buyer runtime exposes the settlement transaction hash, verify it on Base with /receipt/<tx>. Schema: agenttoll.receipt.v1.