Overview
Tako supports the Machine Payments Protocol (MPP) — an open standard for machine-to-machine payments via HTTP 402. This allows AI agents to discover and pay for Tako API access automatically, without requiring API keys or account signup.How It Works
- Discovery — Agents find Tako’s available endpoints at
https://tako.com/.well-known/mpp.json - 402 Challenge — When an agent calls an MPP endpoint without payment, Tako returns
402 Payment Requiredwith pricing info - Payment — The agent pays via Stripe or Tempo stablecoins
- Access — The agent retries with a payment credential and gets the response
Available Endpoints
| Endpoint | Method | Price | Description |
|---|---|---|---|
/api/mpp/v1/search/fast | POST | $0.037 | Fast data search |
/api/mpp/v1/visualize | POST | $0.037 | Visualize data from a search query |
/api/mpp/v1/thinviz/create | POST | $0.004 | Create a ThinViz card from components |
Payment Methods
- Stripe — Pay via Stripe PaymentIntent. Agents need a pre-configured Stripe customer with a payment method.
- Tempo — Pay via Tempo stablecoin on-chain transaction.
Authentication Flow
Paid endpoints
Request format
MPP endpoints accept the same request body as their non-MPP counterparts. For example,/api/mpp/v1/search/fast accepts the same body as /v1/knowledge_search:
Discovery Manifest
Agents can discover all MPP-enabled endpoints at:Idempotency
To handle network failures, include anIdempotency-Key header. If the payment was processed but the response was lost, retrying with the same key returns the cached response instead of charging again.
Error Codes
| Status | Meaning |
|---|---|
| 402 | Payment required — includes MPP challenge headers |
| 400 | Malformed credential or unsupported payment method |
| 409 | Payment credential already used (replay) |
| 401 | Invalid receipt token (poll endpoints) |