/agent/orders endpoint, allowing AI agents to place orders and pay in a single request flow — no Zinc account or API key required.
Why MPP?
Traditional API integrations require account setup, API keys, and a pre-funded balance. MPP removes these steps by embedding payment directly into the HTTP request cycle:- No account needed — Agents pay per-request using standard HTTP headers
- Multiple payment methods — Stripe cards/wallets, Tempo stablecoins, and more
- Built for agents — Designed for automated, machine-to-machine payment flows
How It Works
MPP uses an HTTP 402 challenge-credential-receipt flow:Receive payment challenge
Zinc responds with HTTP
402 Payment Required and WWW-Authenticate headers describing available payment methods and the amount due.Complete payment
The MPP client completes payment through the chosen method (e.g., Stripe checkout, Tempo transfer) and receives a credential.
Resubmit with credential
The agent resubmits the original request with the payment credential in the
Authorization header.Order confirmed
Zinc validates the payment receipt and processes the order, returning a
201 response with order details and two important headers:X-Api-Key— A temporary API key the agent can use to check order status viaGET /orders/{id}without repeating the payment flow.Payment-Receipt— The MPP payment receipt confirming the charge.
Checking Order Status
The201 response includes an X-Api-Key header containing a temporary API key. Use this key to poll the order status without going through the 402 payment flow again:
The
X-Api-Key is scoped to the order it was issued for. Store it after placing the order so your agent can track fulfillment progress.Quick Start
Install an MPP Client
MPP client libraries handle the 402 flow automatically. Official SDKs are available in TypeScript, Python, and Rust.Place an Order
The easiest way to test is with themppx CLI, which handles the 402 payment flow automatically:
Supported Payment Methods
| Method | Description |
|---|---|
| Stripe | Cards and wallets via Stripe |
| Tempo | Stablecoin payments via Tempo |
The available payment methods are returned in the
WWW-Authenticate headers of the 402 response. Your MPP client will automatically select a compatible method.Next Steps
MPP Playground
Try placing an MPP order in our interactive playground.
API Reference
See the full API spec for the MPP order endpoint.
MPP Specification
Read the full MPP protocol specification.

