0tokens
AI inference
Weight input and output tokens differently, one price per thousand.
e.g. $0.002 per 1k weighted tokens
x402Payment-required responses your customers' agents can act on→
Usage-Based Billing,
Usage-Based Billing,
Settled in Stablecoins
Elytra Billing lets APIs, AI products and agents charge per call. Customers approve a spending cap from their own wallet, and we settle what they use in USDC on Solana.
Built for usage
Price the thing
you actually sell
Tokens, rows, seconds or calls. Charges too small for a card, settled together once they're worth moving.
0rows
Data APIs
Bill by the row, the record or the megabyte you return.
e.g. $0.40 per 10k rows
0GPU seconds
Compute
Graduated tiers, so heavy users get a better rate automatically.
e.g. from $0.0004 per second
0calls
Agents and APIs
One charge per successful request. Nothing to report but the call.
e.g. $0.001 per call
How it works
Four steps from first
request to first payout
01
Set your price
Publish a rate card: per token, per row, per call, flat or in graduated tiers. Prices can't drift under your customers. A new price is a new card, and they agree to it first.
02
Your customer sets a cap
Send them to the hosted checkout. They approve a weekly or monthly cap with one signature from their own wallet. Network fees are sponsored, so they need no SOL.
03
Serve, then meter
Before each request, ask if there's room under the cap. After it succeeds, report the usage. Retries never double-charge, and a customer at their cap gets a clear 402 instead of an error.
04
Get paid in USDC
When the usage is worth moving, it's pulled from your customer's wallet to yours in one Solana transaction. You get a signed webhook and a receipt for every settlement.
Your dashboard
Every customer, cap
and payout in one place
See what you're owed and not yet paid, what was pulled and when, and which customers are close to their cap.
Your customers stay in control
Trust that's
built in
Customers see every charge against their cap, get a heads-up before they hit it, and can revoke on-chain in one tap. No card on file and no surprise bills.
- The cap is the ceiling. No more than they approved can ever move in a period.
- Every charge is on their statement, with the usage under it.
- Revoking is theirs. One on-chain call, no support ticket.
For agents
Programs can pay, too
An AI agent approves a cap from its own keypair, with no browser and no human in the loop. At the cap, it reads the 402 and knows whether to top up, wait or re-authorise.
Pricing
0.75%.
That's the price.
No fixed fee per charge, so small charges stay small. A settlement costs about $0.0008 in network fees whatever it moves.
Get startedChargeElytra · 0.75%Typical card · 2.9% + 30¢
$0.10$0.00075$0.30
$1.00$0.0075$0.33
$5.00$0.0375$0.45
$100$0.75$3.20
Fee on one charge. Bars are drawn relative to the card fee on that row.
The parts of billing that usually cost you money, handled
Retries can't double-charge
Each event carries your id. Sending it twice is recorded once.
Signed, ordered webhooks
Every event is signed and retried, and arrives in order.
Our outage isn't yours
If we can't be reached, your requests are still served.
Nobody holds a balance
Money moves from your customer's wallet straight to yours.
Books that reconcile
Every settlement with the usage under it, as JSON or CSV.
USDC and USDT
Each settles and reconciles on its own, never holding up the other.
For developers
Try the whole loop first
A small JSON API at billing.elytra.global. Every signup gets a test key, a funded test customer and forced settlements, so you can see the whole loop before real money moves.
- POST
/v1/rate-cards - POST
/v1/authorisation-sessions - GET
/v1/delegations/:id/headroom - POST
/v1/usage - GET
/v1/settlements
Elytra Billing
Start billing for usage
this week
Frequently
asked questions
For the people wiring it up
Nobody in the middle. Each settlement moves funds directly from your customer's wallet to your payout wallet, inside the cap they signed. Elytra never holds a balance for either of you.
Settlement runs on Solana, in USDC and USDT. Each asset keeps its own books and reconciles on its own.
Usage accrues as you report it. It settles once the amount is worth moving, on a daily or weekly cadence if you choose one, and early whenever money would otherwise be at risk: the customer is near their cap, their balance is falling, or their authorisation is close to renewal. You can read every accrual and settlement over the API.
The headroom check fails open, so your requests keep being served. Usage reports are queued and retried, so late usage settles late rather than being lost.
Yes. A customer can revoke their authorisation on-chain at any time, and you receive delegation.revoked. The cap they signed is the most that can ever be pulled in a period.
Every signup gets a test key. POST /v1/test/buyers returns a funded buyer and a delegation, and POST /v1/test/settle forces a settlement so you can see the amounts and receive the webhook.