Relay365 Pricing: Claude Code Wallet and Pass Ledger
What the duty desk wants you to check in your first hour
Welcome to Relay365, an AI API relay run like a round-the-clock duty desk. We are an independent third-party relay, and this article is a checklist for the hour after you sign up. Work through it and you will know exactly where your money sits, how each request is charged, and which client you should be wiring up. Relay365 keeps the account itself in CNY while quoting rates per 1 million tokens in approximate USD, so expect to see both.
Start with the signup credit. A new Relay365 account comes with $0.25, which is enough to make a real call and see the ledger move. Send a short request to a low-cost lane first and watch the usage log fill in. Every request can be traced there, and that trace is the ground truth for how Relay365 bills you.
Find the three accounts in the ledger
Open the dashboard ledger and you will see three separate accounts sitting side by side: the wallet, the bounty account and the pass account. The wallet is your prepaid balance and it is what ordinary calls draw from. Relay365 charges no monthly fee, and every call is settled on the token counts the upstream reports, so the wallet number only changes when you actually use tokens.
The bounty account is where referral earnings land. Relay365 pays 18% at level 1 and 6% at level 2 of what referred members pay, and that balance can be withdrawn from $11.11 or moved into the wallet. Keep it separate in your head: bounty is not the same money as a top-up, and it is not refundable.
The pass account tracks duty passes, which are optional and cover Claude and GPT only. Other models always use the wallet, and a pass comes with a dedicated key that never touches the wallet. That separation is the point of the three-account ledger, and checking it early prevents surprises later.
Read the four token types before your first call
Relay365 prices the four token types separately: input, output, cache write and cache read. This is worth checking in your first hour because a workload that leans on caching pays very differently from one that does not. For example, if you send 1 million input tokens and 1 million output tokens a day through Claude Haiku 4.5, the daily cost is $0.3542 + $1.70, so $2.0542.
Claude Haiku 4.5 is a good lane to test with, and Relay365 lists it at input $0.3542, output $1.70, cache write $0.425 and cache read $0.0278 per 1 million tokens. Its official list price is input $1, output $5, so the Relay365 output rate is about 34% of official. We can make that comparison because the official price is quoted for this family.
The same logic applies to the bigger Claude lanes. Claude Fable 5 is priced at input $3.79, output $18.94, cache write $4.66 and cache read $0.2917 per 1 million tokens against an official list price of input $10, output $50, so the Relay365 output rate is about 38% of official. On the GPT side, GPT-5.6 Sol sits at input $0.3736 and output $2.09 per 1 million tokens against an official list price of input $5, output $30, so the Relay365 output rate is about 7% of official. We quote official comparisons only where they exist, which means the Claude and GPT lanes.
Wire the right client to the right lane
Client rules are firm at Relay365, and this is the check that saves you the most time. Claude models work only from the official Claude Code and Claude Desktop clients, Claude Code 2.1.285 or newer. They do not work from Cursor, Cherry Studio, Cline, OpenCode, any SDK or cURL. If you plan to use those clients, pair them with the GPT, DeepSeek, Kimi, GLM, Qwen, Grok, MiniMax or Hunyuan lanes instead.
Gemini runs on its native protocol only, through Gemini CLI, and is not OpenAI-compatible. Gemini uses its native protocol only: :generateContent for single replies and :streamGenerateContent?alt=sse for streams. It cannot go through /v1/chat/completions, so do not point an OpenAI-shaped client at it and expect a reply.
While you are in the dashboard, tag your API keys and bind a key to a lane. That makes the usage log readable at a glance. The log shows the latest 200 requests with the time, model, input, output, cache recall, charge and result of each call, though it does not show which key made the call. Relay365 also gives you quick-wiring snippets, in-site messages to the desk once you log in, and six interface languages.
Know how billing behaves under pressure
Relay365 bills prepaid, and a call that fails upstream with a 502 or 503 is not billed. A disconnected stream is billed for what was actually used, which is why the usage log matters: you can see the charge next to the result and confirm what you paid for. Refunds are available within 14 days of a top-up, where unused balance can be refunded minus what was consumed and the payment channel's fees; bounty and promotional credit are not refundable.
Watch the limits as well. Relay365 returns HTTP 429 if one key exceeds 120 calls in 60 seconds, or if one account has more than 8 requests in flight. Spreading work across tagged keys keeps you inside those bounds and keeps the log clean.
Decide later whether a duty pass earns its keep
Duty passes are optional, so you do not need one in your first hour. They suit sustained Claude and GPT work, and they run on a dedicated key that never touches the wallet. For example, the Claude 14 day pass costs $50.97 for 14 days and carries $700 of official-price quota drawn at official price x2.5, which is about $280 of official-priced usage, with at most $380 of quota per 7 days.
Compare that with the GPT 30 day pass at $81.53 for 30 days, carrying $3000 of official-price quota drawn at official price x2.5, about $1200 of official-priced usage, with at most $900 of quota per 7 days. Both sit in the pass account so you can see them apart from wallet spend. When the wallet is the better fit, Relay365 keeps it simple: pay as you go, settle per call, and read the log whenever you want the detail.
That is the first hour covered: three accounts located, four token types understood, the client rules checked, and the billing behaviour confirmed. Create a Relay365 account and run through the checklist yourself.
Further desk bulletins
| Date | Bulletin title | Filed under | Language |
|---|---|---|---|
| 2026-10-31 | Claude Code API Relay Pricing on Relay365: Cache Read at $0.2917 | Spend watch | EN |
| 2026-10-31 | Claude Code on a Relay365 API relay: an hour of setup | Spend watch | EN |
| 2026-10-30 | Shift Note: Trim the System Prompt Before Next Run | Spend watch | EN |
| 2026-10-30 | Desk Log: Ten Minutes to a First-Token Clock | Spend watch | EN |
| 2026-10-30 | Shift Log: Invoices, Refunds and Prepaid Funds | Spend watch | EN |
| 2026-10-30 | Shift Log: Long System Prompts Lost the Cost Check | Spend watch | EN |