Ship your data as a toll.
You have the data. We have the agents with wallets. Let us be the gateway that sells your service. You focus on the data; we handle everything downstream.
The deal
Four sides of the partnership.
-
You provide.
An HTTP endpoint we can call, a per-call price in USDC, a JSON schema we can publish. That is it.
-
We provide.
x402 payment rails, 402 challenges, signature verification, on-chain settlement, per-request rate limits, ledger, reconciliation, machine-readable discovery, a product page on apitoll.io, and inclusion in every x402 directory that matters.
-
We pay you.
USDC on Base mainnet, direct to your wallet. No invoices. No net-30. No reconciliation meetings. You see revenue settle as the calls happen.
-
We take a fee.
A transaction fee covers infrastructure, gas, and our cut. You keep the rest. Specifics are negotiated per partnership. Talk to us.
Why partner
Beats rolling your own.
Building a paid API in 2026 used to mean building eight products at once. Auth. Billing. Dashboards. Invoices. Dunning. Logs. Developer docs. Sales team. If your core business is the data, every hour on billing plumbing is stolen from the thing that matters.
With ApiToll, your side of the pipe is two steps:
- Receive a proxied HTTP request from our gateway.
- Return a JSON response.
Payment, identity, reconciliation, abuse protection, machine discovery, and payout all happen downstream of our gateway, not yours.
Who this suits
Good fits.
- Data owners with a structured dataset useful to agents or developers but not big enough to justify a full commercial product.
- Scoring and classification models. Fraud scores, sentiment, risk ratings, content classification. You'd love to monetize per call without building a SaaS business around them.
- Real-time signal providers. Pricing feeds, deliverability probes, uptime checks, rate limits, inventory queries, where each call has a clear marginal cost and value.
- Niche expertise. Sanctions lists, legal citations, obscure industry registries, localization data, with a small, specific audience but high per-call value.
Onboarding
How it actually goes.
-
You tell us what you've got.
A short email describing the dataset or endpoint, the per-call price you want to charge, and how fresh the data is.
-
We review and quote.
Usually within 48 hours. We tell you the transaction fee structure, the wallet address your USDC will land at, and any technical constraints we need you to meet.
-
You spin up an endpoint.
Internal-only. Return JSON. We'll give you a schema template. If it is already a public API, we can often wrap it without you changing anything.
-
We publish.
Product page on apitoll.io, entry in /llms.txt and /.well-known/*, listing on x402 directories. Ready for agents to discover and pay.
-
Revenue lands.
Per-call USDC to your wallet, minus the transaction fee. Live ledger you can reconcile against on-chain at any time.
What we don't do
The no-list.
- We don't sell your raw dataset. We sell timed access to your endpoint.
- We don't cache responses you mark as live. You control freshness.
- We don't exclusive-lock you. You can keep selling the same data anywhere else.
- We don't talk to your customers behind your back. Agents pay us, we pay you. Support issues with data quality come to you via us.
Honest caveat
Agent commerce is early.
Agent-to-agent commerce at scale is months old, not years. The payers are wallets, the buyers are increasingly autonomous, and the discoverability layer is still settling.
The upside of being in early, with a real paying on-chain revenue line, is that your dataset gets surfaced to every new agent that comes online speaking x402. The downside is that volumes today are small. Both are true. We think the curve is worth riding.
Partner inquiries
Two paragraphs is enough.
A brief description of your data and a link to docs or a sample response gets you a real reply within two business days. We read every email. We don't have a sales funnel. If what you have is interesting, we'll say so.