One key.
One model.
Four counters.
This page is a demonstration of the console with fixed example values. Nothing here is a live account, no number on it is a measurement of your usage, and the key is not real. Numbers move when the page loads because the counters animate; they are not polling anywhere.
sk-rwi-••••-••••-••••-••••
The key is a bearer credential; anyone holding it spends your credit. Regenerating kills the old key instantly, with no approval step and no email confirmation — there is no address on file to send one to.
This chart is drawn from counters: how many, when. It cannot show what was asked.
Last eight calls
Time, model, tokens, latency, status. That is the entire row — there is no column for prompt or completion, because there is no such column.
| Time (UTC) | Model | Tokens in | Tokens out | Latency | Status |
|---|---|---|---|---|---|
| 2026-11-05 14:02:41 | qwen-flash-next | 8,412 | 1,906 | 4.12 s | 200 · ok |
| 2026-11-05 14:01:07 | qwen-flash-next | 2,118 | 744 | 1.94 s | 200 · ok |
| 2026-11-05 13:58:22 | qwen-flash-next | 41,006 | 3,220 | 11.48 s | 200 · ok |
| 2026-11-05 13:55:09 | qwen-flash-next | 612 | 118 | 0.92 s | 200 · ok |
| 2026-11-05 13:54:50 | qwen-flash-next | — | — | 0.00 s | 429 · concurrency 5 |
| 2026-11-05 13:51:33 | qwen-flash-next | 15,290 | 2,481 | 6.73 s | 200 · ok |
| 2026-11-05 13:47:18 | qwen-flash-next | 3,744 | 892 | 2.31 s | 200 · ok |
| 2026-11-05 13:44:02 | qwen-flash-next | 96,512 | 5,004 | 24.86 s | 200 · ok |
Rows are illustrative. The 429 above was rejected before inference, so it is not billed — rejected requests never reach the counter.
Share of traffic by endpoint
Three endpoints exist. Almost everything is the first one. That is not a growth problem, it is the product.
Payments in. Nothing out.
Every transfer that ever credited this key. The list only has one direction, and it keeps that direction permanently.
| Date | Purchased | Amount | Coin · network | Tx | Status |
|---|---|---|---|---|---|
| 2026-11-01 | Unlimited · 30 days | $50.00 | USDT · TRC-20 | 9f2a…c41d | credited |
| 2026-10-02 | Pay as you go · 500 requests | $25.00 | XMR | b71e…09aa | credited |
| 2026-09-28 | Pay as you go · 100 requests | $5.00 | BTC | 41c8…7de3 | credited |
| 2026-09-27 | Top-up attempt · wrong network | $20.00 | USDC · BEP-20 | 5ac0…11fb | not credited |
The last row is a deposit sent on a network this service does not operate — the chain confirmed it, the balance did not move, and nothing was returned.
There is no refund column. No row on this ledger can ever be reversed, credited back, or paid out. If a balance is wrong, it is corrected to match the chain — a bookkeeping fix, not a return of value. Terms §6.
Top up, or change plan
Crypto only. Prepaid credit does not expire, and it does not come back — no refunds, ever, on any balance.
Unlimited does not auto-renew: billing is a crypto transfer, so nothing can be charged automatically. When the period ends, the key falls back to prepaid credit.
Check the network label before you send. A deposit on the wrong network cannot be credited and is not refunded — see support.
Compare plansThe endpoint behind this dashboard
One POST, one header, one model string. The response is OpenAI-compatible, so an existing client usually works after the base URL and the key are swapped.
- Base URL: https://api.rawinfer.com/v1
- Model string: qwen-flash-next — the only one
- Counters: GET /v1/usage, same numbers as this page
curl https://api.rawinfer.com/v1/chat/completions \
-H "Authorization: Bearer $UAM_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "qwen-flash-next",
"reasoning_effort": "off",
"messages": [
{ "role": "user", "content": "Map the attack surface of this service." }
]
}'Retention on this account
Four fields exist for this key: the identifier, a request count, token totals, and timestamps. Prompt text and completions are never written anywhere, so there is nothing to show on this page beyond counters — and nothing to hand over if someone asks.
- Prompts stored: none
- Completions stored: none
- Uploaded media stored: none
- Email on file: none
Deleting the key is permanent. The credential dies, the counters are purged, and the credit on it is not returned — there is no refund for deletion, for suspension, or for anything else. Read Terms §6 before pressing it.
Both controls above are inert in this build. The delete button does not delete anything, because there is no account behind this page.
Demo console · fixed example data · nothing live