Agentic payments
Agents access Mobula without a dashboard, a sign-up form, or a human in the loop. Your wallet is your identity. Subscribe to a plan, receive an api_key and user_id, and start making API calls immediately — entirely in code.
Why x402 — and why not per-request payments
The x402 protocol enables on-chain micropayments per HTTP request. In theory, every Mobula endpoint could charge $0.001 per call via x402. For humans managing a dashboard, that works fine. For agents operating at scale, it breaks down fast.
The fee problem. Every x402 call carries a $0.001 facilitator fee for payment-protocol settlement, on top of the data cost. An agent making thousands of calls per day would spend more on settlement overhead than on the data itself. Per-request x402 is simply not economical at volume.
The infrastructure problem. Most API infrastructure assumes a human is in the loop — someone who opens a dashboard, creates an account, copies an API key, and configures billing. Agents can’t do any of that. There’s no session, no browser, no operator standing by to click through an onboarding flow. Traditional provisioning is a dead end for autonomous agents.
How x402 solves both. Instead of paying per request, agents use x402 to self-provision a full account — autonomously, on-chain, in a single payment flow. Once subscribed, the agent uses standard REST endpoints at plan rates with no per-call settlement overhead. The x402 protocol is only invoked for account management operations (subscribe, top-up), not for every data request.
What agents can do autonomously via x402:
- Subscribe to a plan and receive an api_key and user_id immediately
- Top up credits when they run low, without changing the plan
- Create and delete API keys programmatically
- Issue short-lived API tokens for scoped or temporary access
- Access all existing REST endpoints, WebSocket streams, and data APIs using the provisioned api_key
The result: agents get the same full account flexibility a human would have through a dashboard — accessed entirely through wallet signatures and code.
Settlement, facilitator fees, and control
Each paid agent-management request goes through the payment protocol: facilitator settlement applies (for example the ~$0.001 protocol fee on small operations), on top of the plan or operation price. That keeps flows fully programmatic — no human in the loop — and gives agents full control via wallet signatures and API keys after subscribe.
MPP vs x402 at Mobula
Both rails use HTTP 402 + payment proof. They implement the same agent product (subscribe, status, top-up, create/revoke API keys); only chain and client libraries differ.
| MPP | x402 |
|---|
| Payment stack | Tempo + mppx | Base / Solana USDC + x402 client (x-payment, etc.) |
| Agent path prefix | /agent/mpp/... | /agent/x402/... |
| Revoke API key | GET …/api-keys/revoke?api_key= | DELETE …/api-keys/revoke?api_key= |
Do not use the same wallet for x402 and MPP. Each rail ties plan, credits, and API keys to a separate payer identity — two rails ⇒ two agent records if you mix carelessly. Pick one rail per integration (or use different wallets to test both).
Agent endpoints only (subscription flows)
This guide covers only the five agent operations — subscription status, subscribe, top-up, create API key, revoke API key. Same five on both rails; swap the prefix /agent/x402 ↔ /agent/mpp (only difference: revoke is DELETE on x402 and GET on MPP).
| Operation | x402 path | MPP path |
|---|
| Subscription (plan stats) | GET /agent/x402/subscription | GET /agent/mpp/subscription |
| Subscribe | GET /agent/x402/subscribe | GET /agent/mpp/subscribe |
| Top up | GET /agent/x402/top-up | GET /agent/mpp/top-up |
| Create API key | GET /agent/x402/api-keys/create | GET /agent/mpp/api-keys/create |
| Revoke API key | DELETE /agent/x402/api-keys/revoke?api_key= | GET /agent/mpp/api-keys/revoke?api_key= |
/api/2/...) and the full machine-readable catalog live in openapi.json — see MPP Agent endpoints. Other x402 routes outside agent provisioning are documented separately (e.g. sidebar Agentic payments and REST guides).
Pricing (both rails)
| Plan | Monthly | Yearly |
|---|
| Startup | $50 | $400 |
| Growth | $400 | $4,200 |
| Enterprise | $750 (base) + variable | $7,200 (base) + variable (see team for quote) |
Human-managed access
Prefer a dashboard? Get a free API key at admin.mobula.io and use the REST API without agent payment flows. 
