The service requests payment
HTTP 402 Payment Required: amount and terms, machine-readable.
AgentPay / AI agent payments · x402 & MPP
Payments, built for AI agents.
Your AI agents buy services and settle them on their own, in MAD, on licensed rails — via x402 and MPP, the open standards for machine-to-machine payments.
↓See the protocolIn short
AgentPay is Aslan's payment rail for AI agents. A service answers an agent's request with HTTP 402 Payment Required; the agent pays on its own, in Moroccan dirhams, through the open x402 or MPP standards, and receives the resource with a receipt. AgentPay is currently available as a public sandbox on a test network.
The proof in 60 seconds
Watch an agent settle a payment.
The protocol / 01
One request. One settlement. One receipt.
The agent settles
MAD wallet, a signed operation, no card involved.
Delivered, settled, traced
Settlement on an internal ledger, receipt and webhook.
An agent settles a resource — test network or production
The building blocks / 02
What you compose.
AgentPay runs on Aslan's rails — Principal Agent of a payment institution licensed by Bank Al-Maghrib.
MAD wallet
Pre-funded agent accounts, in dirhams, ready to spend.
x402 facilitator
Verify and settle — the layer that validates and executes every x402 payment.
Receipts & ledger
operationId, statuses, webhooks: every movement leaves a trail.
Pay-ins
Your services sell to agents. The protocol runs both ways.
How it works / 03
From a 402 to a receipt.
- 01
The agent calls a paid resource
An API, a dataset, a service — exposed behind HTTP.
- 02
The service answers 402
Payment Required, with amount, currency and recipient in a machine-readable form.
- 03
The agent pays
With a signed payment (x402) or a capped Agent Payment Token (MPP).
- 04
AgentPay verifies and settles
Checks the payment, blocks replays and settles it on an internal ledger in centimes of dirham.
- 05
The resource is delivered
With a receipt in the response headers and a webhook for the seller.
Key facts / 04
What you can count on.
- Protocols
- x402 (HTTP 402 with an X-PAYMENT header) and MPP (HTTP 402 with WWW-Authenticate: Payment).
- Currency
- Moroccan dirham, in integer centimes.
- Spending limits
- MPP tokens carry a per-charge cap and an optional lifetime cap.
- Replay protection
- Each payment authorisation and each challenge can only be used once.
- Receipts
- X-PAYMENT-RESPONSE or Payment-Receipt headers, plus webhooks.
- Mandates
- AP2 signed mandates can be tried in the sandbox.
- Status
- Public sandbox: a demo wallet with 100 MAD and real transactions on a test network.
Comparison / 05
x402 or MPP?
Both start with HTTP 402. They differ in how the agent proves it can pay.
| x402 | MPP | |
|---|---|---|
| Signal | HTTP 402 with a list of accepted payments | HTTP 402 with a WWW-Authenticate: Payment challenge |
| Agent credential | A signed payment for each request | A reusable Agent Payment Token |
| Spending limits | Set by each signed payment | Per-charge cap and optional lifetime cap |
| Receipt | X-PAYMENT-RESPONSE header | Payment-Receipt header |
| Best for | Pay-per-call, wallet to wallet | Repeated purchases under a budget |
FAQ / 06
Questions builders ask.
How can an AI agent pay for an API?
With a payment protocol built on HTTP. The API answers the agent with HTTP 402 Payment Required and its terms; the agent produces a payment — a signed authorisation (x402) or a capped token (MPP) — and retries the request. AgentPay verifies, settles in dirhams and returns the resource with a receipt.
What is x402?
x402 is an open standard that revives the HTTP 402 Payment Required status code. A server lists the payments it accepts, the client attaches a signed payment in an X-PAYMENT header, and a facilitator verifies and settles it. AgentPay acts as that facilitator for payments in dirhams.
What is MPP, the Machine Payments Protocol?
MPP is an HTTP 402 standard where the server issues a challenge in a WWW-Authenticate: Payment header and the client answers with a credential. In AgentPay, that credential is an Agent Payment Token with spending caps, and each challenge can only be used once.
Can I limit what my agent spends?
Yes. An Agent Payment Token has a maximum amount per charge and an optional maximum total over its lifetime; beyond that, payment is refused. In the sandbox, you can also try AP2 signed mandates, which define what an agent is allowed to buy.
Is AgentPay available in production?
Not yet. AgentPay is currently a public sandbox: a demo wallet with 100 MAD and real transactions on our test network, so you can run the full protocol end to end. Talk to the team if you want to use it with your own services.
Can my service sell to AI agents?
Yes — the protocol works both ways. A service puts its paid routes behind HTTP 402, AgentPay verifies and settles the agents' payments, and every settlement is traced with a receipt, an operation ID and webhooks.
AgentPay / in action
Your agents are ready to pay.
A public sandbox: a demo wallet, 100 MAD, and real transactions on our test network — the full protocol end to end.