Your agent can read the web. Your finance team never holds a stablecoin.
More of the useful web now answers an automated request with 402 — pay, then you may read. The paying part is solved several times over. Whose books the asset sits on is not. Your agents pay for the data they need. You get one AUD invoice.
The ledger the dashboard shows: an agent, a URL, a price, a cap.
Built for the team that signs off
The paying part is commoditised. What procurement actually asks is who holds the asset, who set the limit, and who to call when it goes wrong — so that is what the product is.
- hourly ceiling
- a tenth of the month — a runaway spends in hours, not seconds
- per-key budgets
- a key can spend its own budget and nothing else
- audit trail
- which agent, which URL, what price — bodies never stored
- failed fetches
- refundable by us, because we are the party you bought from — being built
How it works
- 01
Give each agent a key
Every agent gets its own API key, and every key carries its own dollar caps — hourly and monthly. A budget belongs to a name, not to the account.
- 02
Agents fetch through the gateway
A 402-gated API answers with a price. If it fits inside the caps, we pay it on our side, over x402, and stream the response straight back to your agent.
- 03
Every fetch lands on the ledger
Which agent, which URL, what price — recorded as it happens. Metadata is kept; response bodies are never stored.
- 04
One AUD invoice
Spend draws down the included allowance first, then overage at the publisher’s price plus your tier’s margin, plus a small per-request fee. GST on the invoice, purchase-order field on the account.
What you're actually buying
Dollar caps, never request counts
Paid endpoints range across two orders of magnitude in price, so a cap counted in requests is not a budget. Every limit here is denominated in money, per agent, and spend stops where you said.
You never hold the asset
You pay a monthly subscription in Australian dollars. Your agents fetch through our endpoint; we settle each payment on our side, over x402, and stream the response straight back. Nothing token-shaped ever reaches your books.
A failed fetch shouldn't cost you
These payments push irreversibly: pay, receive a 500, and the money is simply gone. Because we are the party you bought from, we can refund you when that happens — which a delegated wallet structurally cannot do. That crediting flow is being built, and nothing about it is running yet.
An audit trail with a name on it
Which agent spent what, on which URL, at what price. We keep the metadata and never store the response body.
A key per agent, a budget per key
Each agent authenticates with its own key carrying its own caps, and the hourly ceiling is a tenth of the month — so a runaway process takes hours to spend a budget, not seconds.
An invoice procurement recognises
One monthly AUD invoice, GST on it, and a purchase-order field. The line items are agents and dollars, which is a sentence a finance team can approve.
A subscription in dollars, with the spend capped in dollars
Every tier carries an included content allowance and per-agent caps, all denominated in money. Beyond the allowance, overage is billed at the publisher's price plus the tier's margin, plus a small per-request fee.
Dev
Prove your agent works before money matters.
- Allowance
- $2 lifetime
- Hourly cap
- $0.20
- Agent keys
- 1
- Overage
- none — spend stops
Build
One product, a few agents.
- Allowance
- $20 / mo
- Hourly cap
- $2
- Agent keys
- 3
- Overage
- cost + 30%*
Team
Agents doing real work, all day.
- Allowance
- $150 / mo
- Hourly cap
- $15
- Agent keys
- 25
- Overage
- cost + 25%*
Business
Fleets, with finance watching.
- Allowance
- $500 / mo
- Hourly cap
- $50
- Agent keys
- unlimited
- Overage
- cost + 15%*
Enterprise
Contracted volume and terms.
- Allowance
- negotiated
- Hourly cap
- negotiated
- Agent keys
- unlimited
- Overage
- negotiated
Included in every tier
- Dollar caps per agent key, with hourly ceilings
- Per-agent attribution and a full audit trail
- One AUD invoice, GST, and a purchase-order field
*Overage is billed at the publisher’s price plus the stated margin, plus a small per-request fee — on very low-priced pages the fee matters more than the percentage, which is why we say it out loud. Dev’s $2 allowance is a lifetime cap, not a monthly refill. All prices in Australian dollars.