Your API can now charge an AI agent per request.
Agents can call your API. They can't pay for it — no card, no contract, no procurement. Neutral Agent Pay fixes that: put a price on an endpoint, and agents pay per call in USDC or EURC, settled on Stellar in about five seconds and arriving as a fiat balance your finance team can reconcile.
GET /v1/forecast?lat=41.39&lon=2.16Host: api.example.com HTTP/1.1 402 Payment Required{ "scheme": "exact", "network": "stellar:pubnet", "asset": "EURC", "price": "0.0012", "payTo": "GCKF…7QW2"} · signing authorization (MPC, no prompt)· spending controls 12.40 / 50.00 EURC this hour GET /v1/forecast?lat=41.39&lon=2.16X-Payment: <signed authorization> HTTP/1.1 200 OKX-Payment-Response: 4f2a9c…e71b{ "tempC": 24.1, "conditions": "clear" }
One HTTP round trip, one signature, settled on Stellar. No account, no invoice, no human.
Every wallet an agent could pay with needs a human to tap approve.
Paying per request on Stellar means signing a Soroban authorization entry. These are the wallets that can do it today — and an autonomous agent paying on every API call cannot wait for someone to approve a browser prompt. That single gap is why agentic payments stay in demos instead of production.
Five steps, and nobody handles a private key.
The endpoint asks to be paid
Your server answers 402 Payment Required with the price, the asset and where to send it. One line of configuration per route.
The agent's wallet signs
A Stellar account held under MPC signs the authorization for the transfer. No prompt, no browser extension, no key sitting on your servers.
Your spending rules run on-chain
Smart contracts check the amount, the destination and how much this agent has already spent this hour. A payment over budget is refused before it costs anything.
Stellar settles it
The payment is submitted and the network fee is sponsored for you. Final in roughly five seconds, for a fraction of a cent.
Finance sees a fiat balance
Every payment is read straight from the chain and mapped to a ledger entry through Wirex. Each fiat line traces back to a transaction hash, and each hash back to the request that caused it.
Both sides of the transaction, in about twenty lines.
You don't learn a blockchain. You put a price on the endpoints you want to charge for, and a budget on the agents you want to let spend.
import { paymentMiddleware } from "@neutralagentpay/sdk"; app.use(paymentMiddleware({ payTo: MERCHANT_ADDRESS, asset: "EURC", routes: { "GET /v1/forecast": { price: "0.0012" }, "POST /v1/analyze": { price: "0.05" } } })); // Paid endpoints, priced per call.
import { NeutralAgentPay } from "@neutralagentpay/sdk"; const pay = new NeutralAgentPay({ wallet: "agent-7f3c", limits: { perCall: "0.05", perHour: "50.00" } }); const res = await pay.fetch(url); // Pays when asked. Stops at the limit.
Those limits are enforced by a smart contract on Stellar, not by the code above — so an agent can't talk its way past them, and neither can a bug in your service.
Six parts, all of them on Stellar.
Payment engine & SDK
The payment handshake, wrapped with retries, confirmations and clear errors. A paid endpoint is a price in a config file.
Spending controls
Smart contracts holding per-agent caps, allowlists, velocity limits and a stop switch. Open source, with deployments you can verify yourself.
Wallets without wallets
Accounts are created and signed from programmatically. Your customers never see a seed phrase, because there isn't one to see.
Dashboard & reconciliation
Live payment monitoring straight from the chain, spending policy per agent, exportable reports and a queue for anything that doesn't match.
Fiat settlement
Wirex turns settled stablecoin into a spendable fiat balance, on regulated rails it already runs on Stellar today.
Neutral by design
Payments that start on another rail still settle on Stellar. No bridging, no liquidity held, no FX exposure — and no lock-in to us.
Charging a tenth of a cent only works if the rail is nearly free.
On most networks per-request payment is arithmetic that never closes: the fee eats the fee. Four properties make this product work on Stellar and struggle almost anywhere else.
Settlement finality, so paying doesn't slow the request down.
Network fee — and it's sponsored, so the agent never holds XLM.
Both issued natively, so European businesses settle in euros.
Spending limits live in a contract, enforced before a payment exists.
Where paying per request changes the business model.
Sell to agents, not to procurement
Data, inference and search providers can open their API to any agent that turns up, charging per call with no sales cycle, no contract and no monthly seat. The long tail of customers you currently turn away becomes revenue.
Give an agent a budget, not a credit card
Agents have to spend to be useful and need a hard ceiling to be safe. Set a limit per call and per hour, enforced on-chain, with every payment traceable back to the request that caused it.
Let services buy from each other
Machine-to-machine commerce without accounts, invoices or reconciliation spreadsheets. Payment settles in seconds and closes the loop into a fiat balance your finance team already knows how to read.
A team that has already shipped on Stellar.
Enterprise blockchain since 2018. Delivered the Wirex–Vottun–Stellar SDK, and this product is built on that foundation rather than from scratch.
Regulated payments platform with 7M+ users and Visa and Mastercard principal membership. Already settles USDC and EURC card payments on Stellar in production.
MPC key management with a policy engine — what makes signing possible without a person, and without a private key on anyone's server.
Put a price on your first endpoint.
Tell us what you'd charge for and we'll walk through the integration with you. If you'd rather read first, the code and the full technical architecture are public.
