Fifty dollars.
One month.
Everything.
Unlimited requests on one key for a month, on qwen-flash-next with 262,144 tokens of context and five calls in flight. Paid in crypto, nothing metered on the far side. If you want a look before you commit to a month, $5 buys a hundred requests.
Fifty dollars. Everything we run.
One key, thirty days, no request counter. If you want a look before you commit to a month, $5 buys a hundred requests.
Unlimited
One key, thirty days, no request counter. Built for agent loops, red-team runs and anything that talks to the endpoint faster than you can watch a dashboard.
- Uncapped requests on one key for the billing month
- Concurrency 5 — five calls in flight, the sixth waits its turn
- 262,144 tokens of context, up to 131,072 tokens of output
- Every effort level and every sampling knob, no metering on the far side
- Fair use: no resale, no key sharing, no proxying for other people
- Cancel by not paying. Nothing to click, nothing to phone
Runs thirty days from confirmation, not from the first of the month.
Try it for $5 — one hundred requests, prepaid in crypto, and the balance does not expire.
$50 is not a subscription. It is a volume discount.
The flat rate is priced against the token-metered market. Here is that arithmetic in the open, so you can see where it stops being a discount.
Market list price for this class of model: $0.80 per million input tokens, $1.60 per million output tokens, blended at a 70/30 input-to-output mix. Checked 2026-11. It is a reference price, not a quote from anyone.
At that blend, fifty dollars buys roughly forty-eight million tokens a month from a metered endpoint. That sounds like a lot until you price the requests this model is built for.
A single call can carry 262,144 tokens of input and return 131,072 of output. Three of those is a million tokens. An agent loop with a large system prompt, a tool-schema preamble and a rolling transcript clears a million tokens in a handful of turns — and it does it while you are asleep. Most loops of that shape pass the monthly metered budget inside a week, then keep billing.
Our card does not move when the context does. A request with four thousand tokens of code in it costs the same as a request with four: one hundredth of five dollars. That is the whole product decision, and it is why the middle card exists.
| Tokens / month | Metered at $1.04 / 1M | Unlimited card | What that volume looks like |
|---|---|---|---|
| 1M | $1.04 | $50.00 | A week of integration testing on short prompts |
| 10M | $10.40 | $50.00 | One agent, ordinary turns, no long transcripts |
| 48M | $49.92 | $50.00 | Break-even. Around here the two billing models cross |
| 150M | $156.00 | $50.00 | Two agents carrying long context, working days only |
| 500M | $520.00 | $50.00 | A loop you left running over a weekend |
Arithmetic on a public list price, not a quote. Prompt caching, batch rates and the other side's own rounding all move the middle column. The break-even sits near 48M tokens a month either way. Vendor-reported list price, checked 2026-11. Not a measurement of this endpoint.
Five coins, four chains, no processor in the middle.
Card payments are not accepted here, and no payment processor sits behind this page either. You send coin to an address, we credit the key when the transfer settles.
Cards are refused. Processors are refused. Chargebacks do not exist.
A payment processor is a third party that can read your billing details, hold your money for six weeks, and reverse a charge after the work is done. Every one of those is a reason we are not connected to one. A hosted checkout page is a third party too, so there is not one of those either: the address is generated on the checkout page and the funds go straight to a wallet we hold the keys for.
The trade is symmetrical and you should be clear about it before you send anything. A crypto transfer is final in both directions. We cannot pull it back from you, and you cannot pull it back from us. There is nobody to appeal to, because there is no intermediary to hear the appeal.
Addresses rendered on the checkout page are placeholders in this build. In production they are generated per order and expire with the quote.
See the checkout pageThe whole rulebook, in one table.
Read this before you pay. Nothing in it is negotiable later, and none of it is buried in a document you would have to scroll for.
| Rule | Settlement | Why it is written that way |
|---|---|---|
| Paid credit | never expires | Credit bought today still spends after the next redesign of this site. Prepaid balance is prepaid balance. |
| No free credit | never issued | No tier is free, no signup credit exists, and no request is served before a payment confirms. Every request on a key was paid for up front. |
| Crypto transfers | irreversible | We hold the keys, not a bank balance. There is no mechanism in the protocol for a reversal and none in our process either. |
| Wrong network or wrong asset | lost | A USDC balance sent on the Tron network arrives at an address that cannot spend it. It is not recovered and not credited. |
| Underpayment | not credited | An order is either funded or it is not. A short transfer does not buy a partial key and is not returned. |
| Overpayment | not returned | The extra lands in the key's balance as credit. It is not paid back out, because paying out is the thing this architecture exists to avoid. |
| Downtime | no make-good | The status page is the record. There is no credit issued for hours the endpoint was down, and no compensation of any other kind. |
| Key sharing | voids unlimited | One key, one operator. Reselling or pooling a key breaks the fair-use clause on both cards, and the key is disabled. |
| Liability | capped at what you paid | Capped at the amount paid in the preceding thirty days. Build no expectation of a larger number than that. |
| Legality where you live | yours | You are the operator. What you generate, who you generate it for, and whether it is legal in your jurisdiction are all yours. |
No company, no legal entity, no jurisdiction claimed. The full text is in Terms and Privacy & ZDR.
Running this at fleet scale?
Higher volume, more concurrency than five, a second key for a team, or a dedicated endpoint are all negotiable — by email, with a human, at the address on the support page. Terms are monthly and prepaid in crypto. There is no sales team, no procurement portal, no purchase orders and no invoicing system to wait on.
Bring the shape of your traffic: requests a month, average input length, average output length, and how many you need in flight at once. That is enough to price it in one reply.
- Requests per month, rounded up
- Average input and output tokens per request
- Peak concurrency you want in flight
- Whether you need more than one key
- The chain you intend to pay on
Volume terms are still paid in crypto, and a larger invoice does not change the payment rail: one wallet address, one confirmation.
Answered plainly.
Why crypto only?
Because every card processor is a company that reads your billing details, decides what your business is allowed to sell, and can reverse a transaction weeks after the service was delivered. This endpoint answers questions that most processors would classify as a terms violation to even host. We would be deplatformed within a month of the first volume.
Crypto removes the intermediary and inherits its consequences: transactions are final, support cannot reverse anything, and there is nobody to complain to about a payment you regret. That is the deal.
What counts as a request?
One POST /v1/chat/completions call is one request, whether it streams or returns in one piece, whether it is six tokens long or a quarter of a million. There is no token meter pointed at your account and no second count for reasoning effort.
Long context is not surcharged, which is the entire reason a flat month exists here. On a month of unlimited, the count stops mattering altogether.
What does concurrency 5 mean in practice?
Five requests may be in flight against one key at the same time. The sixth waits its turn or comes back with a rate-limit response, depending on how your client is written. Sequential code — one call, wait, next call — never notices the limit at all.
The limit exists so that one loop cannot own the GPUs while everybody else queues behind it. If you need more than five in flight, that is a volume conversation, not a plan upgrade.
Does my credit expire?
No. Paid credit does not expire. Credit bought today is still spendable after the next redesign of this site, after a price change, and after a year of neglect. It sits in the key's balance until requests consume it.
There is no second kind of credit that behaves differently, because no free credit is ever issued. Everything on a key was bought with crypto, and bought credit keeps its request count until it is spent.
Fifty a month.
Take the whole engine.
Create an account, get a key in the browser, and put thirty days of uncapped requests behind it. If you would rather look first, $5 buys a hundred requests and never expires.
One model. One endpoint family. One price.