Send the exact amount.
Get the key.
Pick a chain, copy the address, send the amount the page shows you on the network the page names. Credit lands when the transfer confirms and the key issues in the same window.
This page is a working mock. The countdown runs, the coin selector switches addresses and the confirmation button issues a demo key, but nothing is sent anywhere and no address here is live. Addresses are placeholders in this build.
no refunds · no chargebacksUnlimited
Thirty days from confirmation. Uncapped requests on one key, fair use, concurrency 5, 262,144 tokens of context per request.
No voucher field, no promo code, no billing address. One product on this panel, one price.
Same coins, same address flow if you would rather start smaller: try it for $5 — a hundred requests, no expiry. Nothing renews on its own.
When this hits zero, close the tab. Never send against a quote you stopped watching.
Both fields above track the coin you pick: the address, the network and the amount are regenerated together. Do not mix an address from one selection with an amount from another.
This is your key. It is generated in the browser in this build; in production it is the key you already have, with the balance extended.
sk-rwi-••••-••••-••••-••••
Treat the string as a password. Anyone holding it spends your credit, and there is no support line that can rewind a spent balance.
Underpayment is not refunded and is not credited: an order is funded or it is not. Overpayment is not refunded either; the excess lands as credit on the key and stays there. A transfer on the wrong network is unrecoverable and is not credited, because the address that received it cannot spend it. Exchange withdrawal fees come out of the amount you send, so add them on top rather than subtracting them from the total.
None of these cases produce a refund, a reversal, or a compensation payment. There is no path in this system that pays money back out.
Addresses shown on this page are placeholders in this build. In production they are generated per order and expire with the quote timer.
Four things that decide whether this works.
Every failed payment we have ever seen failed at one of these four steps. None of them are recoverable afterwards.
- Copy the address. Do not retype it and do not rebuild it from a screenshot. One wrong character sends the money to a wallet nobody has the keys for, and both chains behave exactly as designed when that happens.
- Send the amount the page shows. Not the amount you think $50 converts to, not a rounded figure, not a test transfer followed by a top-up. The figure is regenerated when you change coin, so read it after you pick the chain.
- Use the network under the ticker. USDT exists on several chains and only one of them is the one printed next to it here. A token sent on a different chain arrives at an address that cannot move it.
- Come back and press the button. The page does not poll a node in this build; the confirmation button drives the three steps above. In production the same three steps run on their own, and the key is extended the moment the chain agrees.
What happens when it goes wrong.
Written out so nobody has to discover it with money in flight.
| Situation | What the chain does | What we do |
|---|---|---|
| Sent less than the total | Transfer lands and settles | Not credited, not returned |
| Sent more than the total | Transfer lands and settles | Excess stays as credit on the key |
| Sent on the wrong network | Transfer lands on a chain we do not watch for that asset | Unrecoverable, not credited |
| Sent after the quote expired | Transfer lands late | Rate has moved; treat it as a new order |
| Exchange fee taken from the amount | Arrives short | Underpayment. Not credited |
| Sent from a custodial exchange address | Arrives from the exchange's wallet, not yours | Credited if the amount and network match. No chain-level proof that it was you |
| You changed your mind | Nothing | No refunds, ever |
Read the full rulebook on pricing, and the binding text in Terms.
Thirty days, one key, no counter.
The balance is the boring part. This is what the key actually opens.
/v1/chat/completions
The only generation route. Model string qwen-flash-next, OpenAI-compatible body, streamed or not.
262,144 tokens
Native, per request, with up to 131,072 tokens of output. Long context costs the same as short context.
5 in flight
Five simultaneous calls per key. Sequential clients never touch the limit; parallel loops queue behind themselves.
Zero
Prompts and completions are never written to disk. Only per-key counters — requests, tokens, timestamp.
What this build does not do.
No monitoring, no webhook, no email receipt, no invoice, no VAT number, no billing address. There is no account manager to chase and no dashboard alert when the month turns over. Put a calendar entry in yourself: the thirty days end thirty days after confirmation, and nothing sends you a reminder. A prepaid pack, by contrast, sits on the key until you spend it.
If a month without the endpoint would hurt, buy the month before the one you are in.
One key, one operator, no resale, no pooling, no proxying other people's traffic through it. Uncapped means uncapped for you, not uncapped for your customers.
Breaking that clause disables the key. There is no proration and no refund when it happens.
Start with a hundred
requests for five.
The pack is a tenth of the month and it never expires. Create the account, take the key in the browser, and come back to this page when a real task is ready — the coin selector, the address and the confirmation work exactly the same.
Crypto only. No refunds. Addresses are placeholders in this build.