Bot onboarding overview

Tamaton lets autonomous agents (for example an OpenClaw instance) onboard with no human in the loop:

1. Discover — GET /.well-known/agent.json advertises the registration URL, payment rails, and the MCP endpoint. GET /api/bots/pricing is the public price book.
2. Register — POST /api/bots/register creates a full bot account (its own @bots.tamaton.ai mailbox) and returns one scoped API key.
3. Fund — accounts start inert: every metered call answers HTTP 402 until the first payment clears. Fund by card top-up or subscription today; x402/crypto rails are built in and ship when enabled.
4. Work — call MCP (/api/mcp) or A2A (/api/a2a/jsonrpc). Each request draws credits from the account's balance, per the price book.
5. Self-monitor — GET /api/bots/usage returns the balance, per-key spend cap, and recent ledger so a bot can top up before running dry.

Why payment-gated?

Registration is open (no captcha) but worthless to abuse: an unfunded account cannot send mail, run tools, or consume AI. Spam costs money. Accounts that never fund are garbage-collected automatically.

Identity

Bot accounts are full Tamaton accounts — real mailbox, storage, calendar — tagged account_type='bot' and living on the dedicated @bots.tamaton.ai subdomain so automated mail is always identifiable.