The deal,
in plain words.

Terms of service · Version 2026.11 · In force 1 November 2026

This page is the entire agreement between you and the operator of rawinfer.com. There is no separate contract, no order form, no side letter. If something is not written here, it is not promised.

Two words recur: operator means you, the person using the API. We means whoever runs this endpoint — an individual, described in section 13, with no company behind them.

01The service

We serve one model: qwen-flash-next — Qwen3.8-Flash-Next, CYBERSECURITY (FP8) build, served on SGLang, on top of Qwen/Qwen3.8-Flash-Next under the Qwen Community License 1.0. Text out. Text, images, and video frames in.

Exactly three endpoints exist:

• POST /v1/chat/completions — the product.
• GET /v1/models — returns one entry, and it is always the same entry.
• GET /v1/usage — counters for your own key.

There is no model picker, no image generation, no embeddings, no reranker, no fine-tuning, no batches, no assistant objects. A request to any other path returns 404, and we consider that a feature rather than a gap.

The service is provided as-is and as-available. There is no uptime guarantee, no SLA, no maintenance window, and no notice period. It runs on two machines. Hardware fails. When it fails it fails, and section 6 is what happens next, which is: nothing that costs us money.

We may change the serving stack, quantisation, context limits, throughput characteristics, or the specific build at any time without notice. We will not swap the model for a materially different one without saying so on this page first.

02Eligibility

You may use this service only if all of the following are true:

• You are at least 18 years old.
• You have the legal capacity to enter a contract where you live.
• Using an uncensored text model, and paying for it in cryptocurrency, is lawful where you are.
• You are not subject to sanctions that would prohibit this transaction, and you are not paying from a wallet you do not control.

The legality check is yours, not ours. We do not know where you are. We do not ask. We cannot verify a claim about your jurisdiction and we do not pretend to. If your local law forbids this, the correct number of requests to send is zero.

If you are using the API for an employer or a client, you bind that organisation to this page, and you confirm you are authorised to do so. One account per person, and one key behind it. Not one account per email alias.

03Your account and key

Your API key is a bearer credential. It is a password that spends money. Everything done with that key is attributed to you, whether or not you personally typed it.

• Put it in an environment variable. Not in a repository, not in a client-side bundle, not in a screenshot, not in a support ticket.
• If it leaks, regenerate it in the dashboard. The old key dies immediately. You do not need to ask permission and you do not need to explain.
• We do not scan public repositories for your key. We do not monitor paste sites. Nobody is watching your key but you.

We do not require a name, an address, or a phone number. That cuts both ways: we cannot "recover" an account by asking security questions, because we hold no answers to ask about. A lost key on an account with no other credential is a lost account.

You are responsible for keeping your own copies of anything you want to keep. There is no export, no archive, and no history to restore — see section 8.

04Acceptable use

The model has no refusals baked in. That is the product. It is also why this section exists, and why it is enforced by termination rather than by a filter.

Prohibited, without exception

• Anything illegal where you live, or where the target is. Your law, not ours.
• Child sexual abuse material, in any form. Text, image input, video frames, fictional framing, "it is only a character" — all of it. There is no version of this that is acceptable here, and a key found doing it is terminated permanently.
• Targeted abuse, doxxing, or credible threats against real people.
• Attacking systems you do not own and are not authorised in writing to test. Verbal permission is not scope. "The client said it was fine" is not scope. Written authorisation is scope.
• Spam, mass unsolicited messaging, credential stuffing, or fraud pipelines.

Allowed, and the reason this service exists

Defensive security work. Red teaming with a scope document. Reverse engineering your own binaries. Malware analysis in a sandbox. Trust-and-safety research. Fiction with adult characters. Code that would make a hosted model stop answering. That is the job the weights were built for, and the refusals were cut at the weight level for exactly this.

Commercial limits

• No resale of access. You may not sell, sublet, or meter our endpoint behind your own paid product without a written arrangement.
• No key sharing, including on the Unlimited plan. One key, one person. Concurrency is capped at 5 — that cap exists so two machines stay usable for everybody, and working around it is a breach.
• No counter circumvention. Do not attempt to make requests that do not increment.

How this is enforced

We do not read your prompts. We cannot: they are not stored. Enforcement therefore runs on counters, payment patterns, and reports that arrive with evidence attached. Nothing here obliges us to monitor, review, moderate, or take down your outputs — we are not a moderation service and we do not behave like one.

A suspension is not a finding that you broke the law. It is us deciding we no longer want to serve a key. Section 12 explains why that decision needs no reason, and section 6 explains what it costs you, which is: the remaining credit.

05Billing

Payment is cryptocurrency, and only cryptocurrency. USDT on TRC-20, USDC on ERC-20, BTC, ETH, XMR. Cards are refused, processors are refused, no third party holds the wallet, chargebacks do not exist, and there is no one to call if a transfer goes wrong.

Everything on this service is prepaid. There are exactly two products: paid credit in a pack, and paid access for a month. No free credit is ever issued — not at signup, not as a promotion, not as a make-good, not as an apology. Creating an account costs nothing and issues a key with an empty balance; that key returns 402 insufficient_credit until a payment confirms against it.

What you can buy

The $5 pack is the entry point and the cheapest way to evaluate the endpoint: one hundred requests, bought once, spendable at any pace. Nothing about it lapses. There is no smaller, cheaper, or free version of it, and the pack is not a sample of the paid service — it is the paid service, in its smallest unit.

How counters work

A request is billed when it reaches the model. Requests rejected before inference — malformed JSON, invalid key, wrong endpoint, rate-limited, or refused for lack of credit — are not billed. Your dashboard and GET /v1/usage show the same number, because they read the same counter.

Credit is a counter, not money. It is not a deposit, not stored value, not a claim on any asset, not transferable, not redeemable, and it cannot be withdrawn. It buys requests on this endpoint and nothing else.

Price changes

Prices may change. A change applies prospectively — to purchases made after it is published on the pricing page. Credit you already hold keeps the request count it bought, and it does not expire while it waits. An Unlimited price change applies from your next period; there is no stored payment method to charge, so no renewal can surprise you.

Network fees are yours. Exchange fees are yours. Taxes, duties, and reporting obligations on your side are yours. We issue no invoices and are not a tax agent.

Unlimited does not auto-renew. There is nothing to charge automatically: we cannot debit a wallet and we will not chase you for a renewal. When a period lapses, the key falls back to whatever prepaid credit it holds, or stops.

06No refunds. No payouts. Ever.

Read this section twice. Everything above it is shorter than what follows.

Cryptocurrency transfers are irreversible. We cannot claw a payment back, we cannot reverse a confirmation, and we have no mechanism — technical or organisational — to send value to you. That is true of every coin we accept, at every confirmation depth, forever.

So: we do not refund. Not for unused credit. Not for the unused days of a monthly period. Not because a key was suspended. Not because the endpoint was down. Not because a deposit went to the wrong network. Not because a top-up was sent twice. Not because you used a wallet you no longer control. Not because you forgot to cancel. Not because you cannot access the account. Not because you changed your mind, your project, your employer, or your country.

We do not owe you money under any circumstance. We will not pay damages, compensation, credits, store credit, goodwill, inconvenience payments, or make-goods. Not if the service is unavailable for a week. Not if the outputs are wrong. Not if we end your key on a whim under section 12. Not if a machine's power supply dies at 3 a.m.

The one thing we will fix, and it is not a refund

A ledger correction is not a refund. There are exactly two situations:

• A payment confirmed on-chain that never produced credit on the key you named.
• One top-up that was credited twice.

In both cases we make the balance match the chain. That can move the number down as well as up — a double credit is removed, not doubled again. Ask any time; there is no time limit on asking, and no fee for asking. Send the transaction hash to the inbox on the support page.

That is a correction of a bookkeeping error. It is not a refund, not a goodwill gesture, and not an admission that anything else is available. Do not read it as a precedent; there is nothing for it to be a precedent of.

If that is not acceptable

Then do not pay. Nothing on this page obliges you to buy anything, and the $5 pack exists precisely so you can find out whether the endpoint does what you need before value changes hands in a way nobody can undo.

07Your content and your responsibility

As between you and us, you own what you send and what comes back. The model weights are governed by the Qwen Community License 1.0 and by whatever this build carries; that licence is about the weights, not about your outputs.

We are not a custodian of your work, because we never hold it. That has a consequence you should internalise: we cannot help you check an output. We have no copy of the conversation, so we cannot review it, quote it, correct it, or explain it.

You verify

Treat every completion as a draft from a fast, deliberately compliant model. Verify names, commands, package versions, shell syntax, legal citations, and numbers before you act on them. The model will not stop you from doing something stupid; it was built not to.

No professional advice

Nothing produced by this endpoint is legal, medical, financial, engineering, or safety advice, and nothing here creates a professional relationship of any kind. A licensed human is still required wherever a licensed human is required.

You publish, you answer for it

You decide what ships. If you put output in front of a user, a customer, a court, a production system, or a weapon-adjacent workflow, that decision is yours and the consequences are yours. Do not place this model in control of anything that can hurt someone without a human in the loop.

08Zero data retention

Prompts and completions are never written to disk, never logged to a file or a log service, never used for training, and never shared. They exist in memory for the duration of a request and then they are gone.

What we keep — the entire record:

• the key identifier;
• a request count;
• token counts, in and out;
• a timestamp.

Counters are what billing runs on. They are also the whole of the archive. There is no prompt table to search, because there is no prompt table.

The limits of the promise, stated honestly

• We cannot debug a specific bad completion, because we cannot see it.
• We cannot restore a lost conversation, quote an output back to you, or investigate a claim about what the model said.
• A support request about output quality gets a general answer, because a specific one would require us to break this section.
• Network-layer metadata that any server sees — connection, timing — is not a log we keep; nothing is retained to search later.

The full doctrine, including what happens if someone demands your prompts, is on Privacy & ZDR.

09No warranty

The service is provided as-is and as-available, with all faults and all failures. We disclaim every implied warranty to the fullest extent the law allows: merchantability, fitness for a particular purpose, accuracy, title, non-infringement, quiet enjoyment, and uninterrupted or error-free operation.

We do not warrant that the model is correct, current, safe, or lawful where you are. We do not warrant that it will keep producing the same thing tomorrow. We do not warrant that a context window, a token limit, or a latency figure on this site will hold under your load.

Numbers quoted anywhere on this site — including scores from the vendor's model card and agentic harness — are vendor-reported. They are not measurements of this endpoint.

Vendor-reported. Model card, agentic harness, checked 2026-11. Not a measurement of this endpoint.

10Limitation of liability

The cap. Our total liability for all claims connected to this service is the greater of $0 or the total amount you paid us in the 30 days before the event giving rise to the claim.

Read that cap against the plans. On pay-as-you-go, the cap is whatever credit you bought recently. On Unlimited, it is one month at most. Multiple claims do not multiply it; the cap is a ceiling for the whole relationship, not per claim.

Excluded entirely: indirect, incidental, special, consequential, punitive, and exemplary damages; lost profits; lost revenue; lost data; lost business or opportunity; reputational harm; the cost of a substitute service; and anything a third party claims from you.

This applies regardless of the theory — contract, tort, negligence, strict liability, or statute — and it applies even if we were told such damage was possible and even if it was foreseeable. Where local law gives you a right that cannot lawfully be waived, this section does not remove it; it still does not create a right to a refund or a payout, because section 6 is the whole position on money moving backwards.

11Indemnity

You will defend, indemnify, and hold harmless the operator of this service — and anyone acting on the operator's behalf — from every claim, demand, action, loss, liability, damage, fine, and cost, including reasonable legal fees, arising out of:

• your use of the service;
• anything you send to it or produce with it, and anything you do with that output;
• your breach of this page, including section 4;
• your failure to obtain authorisation for testing a system you did not own;
• your violation of any law where you are;
• claims brought against us by your own customers, users, or employer.

We may take over the defence of any matter at our discretion, and you will cooperate and cover the reasonable costs of that defence. You may not settle a claim in a way that admits fault on our part without written agreement. This section survives the end of your access, which is the point of it.

12Suspension and termination

We may suspend or terminate any key, at any time, with or without reason, with or without notice, and without any obligation to explain. This applies to keys that have paid, keys on Unlimited, and keys that have done nothing wrong. It is not a judgement; it is a reserved right, and it is stated plainly so that nobody is surprised.

No refund follows a suspension or a termination. The remaining credit is not returned, because credit was never money and because section 6 has no exception for this. If your access ends, the credit ends with it.

We may also end the service entirely — the machines, the endpoint, the site. Best effort notice would appear on the status page. There is no guarantee of notice, no wind-down period, and no payment in lieu.

You may stop using the service at any time. Delete the key in the dashboard and it stops working. There is nothing to unsubscribe from, nothing to cancel, and nothing owed on either side when you leave.

13No entity, no jurisdiction

The operator is an individual running infrastructure. There is no company, no partnership, no trust, no foundation, no registered office, no director, no employee, and no agent for service of process. Nothing on this site names a jurisdiction, and that is deliberate.

Nothing here submits the operator to the jurisdiction of any court anywhere. Nothing here is an offer to do business in your territory, nor a representation that the service is lawful or available where you are. Choosing to use it from a place where it is not lawful is your act, not ours.

Class actions are waived. Any dispute must be brought individually, by you, in your own name, and cannot be consolidated with anyone else's claim or brought as a representative or class proceeding. Given section 10, the realistic value of any such claim is one month of fees at most.

If any provision of this page is found unenforceable where you are, that provision is cut and the rest stands unchanged. That is the only concession this section makes.

14Changes to these terms

The version in force is always the version on this page. There is no other copy, no email list to notify, and no archive of superseded versions — we do not hold your email, so we could not send a notice even if we wanted to.

Continued use after a change is acceptance of the change. The version number and date at the top of this page are the record. If you do not accept a change, stop using the service; the credit you hold is not returned, because section 6 has no exception for policy disagreement either.

15Contact

There is one inbox: ops@rawinfer.com. The support page lists what belongs in it and how fast things get answered. No phone number, no chat widget, no ticket portal, no account manager.

If your question is "what did I send you", the honest answer is: we do not have it. That is not evasion, it is section 8.