Payments in USDC on
How it works
Three steps, and no code on your side. Callers pay with any x402 client; x402 is an open standard for payments over HTTP.
- 1
Put your API behind Kobaru
In the console, point a route at your endpoint and set a price, like $0.01 per call. Your backend stays as it is.
- 2
A caller hits your API
Without a payment, it gets HTTP 402 Payment Required, with the price and the wallet to pay.
- 3
It pays and gets the data
The caller's client signs a USDC payment and retries. Kobaru checks and settles it, then forwards the request to your API, all within seconds.
# No payment: Kobaru answers with the price
$ curl -i https://access.kobaru.io/acme/price
HTTP/2 402 Payment Required
PAYMENT-REQUIRED: eyJ4NDAyVmVyc2lvbiI6Miwi…
{ "accepts": [{ "network": "eip155:8453", "amount": "10000", … }] }
# The x402 client pays $0.01 and retries
$ curl -i -H "PAYMENT-SIGNATURE: eyJ4NDAy…" https://access.kobaru.io/acme/price
HTTP/2 200 OK
PAYMENT-RESPONSE: eyJzdWNjZXNzIjp0cnVl…
{ "symbol": "BTC", "price": 67250.12 }Built for APIs that sell data or inference
If each call to your API has a cost and a value, charge for it per call, from anyone, without signing them up first.
Sell data by the request
Market data, enrichment, search or scraping results: charge for each lookup instead of selling monthly plans.
Price per call
Charge a fraction of a cent per lookup, which card fees make impossible.
No sign-up wall
New customers pay on their first request, without creating an account or getting an API key.
Keep your API as it is
The paywall sits in front of your existing endpoints. No backend changes.
Sell inference by the call
Models, embeddings, transcription or image generation: charge for each call, priced by route.
Price by route
Give each model or endpoint its own price, so expensive calls cost more.
Checked before it runs
Kobaru checks the payment before the request reaches your API, so unpaid calls never use your compute.
No billing to run
No invoices, usage reports or overdue accounts: each call is paid when it happens.
Get paid by AI agents
Agents can't fill a sign-up form or type a card number. With x402 they pay for each call on their own.
Agents pay on their own
Any agent with an x402 client and a USDC wallet can call your API and pay, with no human in the loop.
Easy to find
List your endpoints in the x402 discovery catalog, where agents look for paid APIs.
One endpoint for everyone
Apps and agents call the same URL at the same price. There is no separate integration to build.
Why not cards or API keys?
Card payments and monthly plans were built for people buying things a few times a month, not for thousands of small calls.
Kobaru uses x402, an open standard that adds payments to HTTP: a server answers 402 Payment Required with a price, and the client pays and retries. How x402 works
What Kobaru handles for you
Everything between a caller paying and your API answering.
Price per route
Set a price for each endpoint in the console and change it whenever you want. Paid requests go through; unpaid ones get a 402 with the price.
No gas to manage
Callers pay your price in USDC and Kobaru pays the network fees. You don't need to hold other tokens or watch gas prices.
Every payment in one place
See each payment in the console: amount, route, network and the on-chain transaction, ready to reconcile.
Transparent Execution
Monetize any API without rewriting a single line of backend code. We abstract all payment complexities for developers who value their time.
Runs at the edge
Payment checks run in data centers close to your callers, so the paywall adds as little latency as possible to each request.
Non-custodial
Payments go from the caller's wallet straight to yours. Kobaru never holds your money, and every payment can be checked on chain.
Integration Options
Choose the integration method that best fits your business needs. From SDKs to direct APIs, we've got you covered.
Standard SDK
Fully compliant with x402 v2. Use the open-standard SDK to accept micropayments with minimal code changes. Our APIs are built to spec, ensuring you stay compatible with the global ecosystem.
Explore docsTransparent Proxy
No backend changes required. Deploy our edge-native proxy to handle authentication, validation, and dynamic routing automatically. Ideal for legacy APIs and high-frequency data streams.
Learn moreDirect API
For those who want absolute control. Our RESTful APIs provide complete customization and direct interaction with Kobaru's infrastructure.
View API referenceSimple, transparent pricing
Kobaru is free during early access: no fees on your payments while we build with our first users.
No account needed
- x402 verify and settle endpoints
- Solana, Base and SKALE
- Network fees (gas) covered
- No sign-up, rate-limited
Free during early access
- Paywall in front of your API, no code
- Console with every payment
- Price per route
- Direct support from the team
Payments are mission-critical. Kobaru's founder has spent more than 15 years building payment products, so that charging per call is as dependable as the API you sell.
Payments for the APIs that apps and agents call
Frequently asked questions
Everything you need to know about Kobaru