GPT-5.6 Sol on Relay365: API relay pricing and first call
Handover note from the Relay365 duty desk
Colleague, the duty desk is handing this note straight to you. You are about to try GPT-5.6 Sol on Relay365, and the whole start-up sequence fits on one page: the wire name, the rates, the billing behaviour, and the shape of your first call. Relay365 is an independent third-party relay run like a round-the-clock duty desk, and it keeps every lane on one table so you can compare models without hopping between providers.
Begin by creating a Relay365 account. A new account receives $0.25 in signup credit. The account itself is kept in CNY, while the rates on the table are per 1 million tokens in approximate USD. Billing runs through a prepaid wallet with no monthly fee, and every call is settled on the token counts the upstream reports, so the charge follows the same numbers the model actually produced.
Two rules from the desk are worth memorising before you write any client code. If a call fails upstream with a 502 or 503, it is not billed. If a stream disconnects, you are billed for what was actually used. A request that never produced a result is not charged.
What GPT-5.6 Sol costs on the Relay365 table
GPT-5.6 Sol arrives on the wire as gpt-5.6-sol, and its Relay365 rates are input $0.3736, output $2.09, cache write not listed, and cache read $0.0292 per 1 million tokens. For reference, the official list price is input $4, output $20, cache read $0.4, which puts the Relay365 output rate at about 10% of official.
Relay365 prices the four token types separately: input, output, cache write and cache read. That separation is what makes the table readable. On GPT-5.6 Sol a cache read costs $0.0292 per 1 million tokens, so repeated context the model can recall is far cheaper than sending the same material as fresh input at $0.3736.
For example, if you send 1 million input tokens and 1 million output tokens a day on GPT-5.6 Sol, that is $0.3736 + $2.09 = $2.4636 a day, or about $73.91 for 30 days. Cache reads, where your setup supports them, sit well below either line.
The same table also carries GPT-6.1 Sol at input $0.1986, output $0.9944 and cache read $0.0389, with the output rate at about 10% of the official list price of $10. GPT-6 Astra is listed at input $0.7444, output $3.72 and cache read $0.075, with output at about 7% of the official list price of $50. On the other side of the table, Claude Fable 5 is priced at input $3.79, output $18.94, cache write $4.66 and cache read $0.2917, with output at about 38% of the official list price of $50, and it runs only from the official Claude Code and Claude Desktop clients, with Claude Code 2.1.285 or newer.
The pricing page shows the full table; this note quotes only the lanes that matter to your first hour on Relay365.
The wire name and your first call
Your first request on Relay365 is short. Create an API key, give it a tag so you can recognise it later, bind it to the GPT lane, and send a small test request with the model field set to gpt-5.6-sol. GPT lanes pair with OpenAI-style tooling, so Cursor, SDKs and cURL are all on the allowed list for this lane.
Keep the request small and watch the usage log as it lands. The log shows the latest 200 requests with the time, model, input, output, cache recall, charge and result of each call. Note one honest limitation: the log does not show which key made the call, so tag your keys carefully and keep one key per experiment while you are learning the shape of the traffic.
Two limits sit on the desk clipboard. A key that sends more than 120 calls in 60 seconds will meet HTTP 429, and an account with more than 8 requests in flight will also meet HTTP 429. If you meet that status while testing, back off rather than retrying in a tight loop.
Cursor, Cherry Studio, Cline, OpenCode, any SDK and cURL pair only with GPT, DeepSeek, Kimi, GLM, Qwen, Grok, MiniMax and Hunyuan lanes. Gemini runs on its native protocol only, through Gemini CLI, using :generateContent for single replies and :streamGenerateContent?alt=sse for streams, and it cannot go through /v1/chat/completions.
Wallet or GPT duty pass
Most colleagues start on the prepaid wallet, top up what they need, and watch the ledger. If your volume is steady and predictable, the GPT duty passes are worth a look. A pass comes with a dedicated key that never touches the wallet, so pass traffic and wallet traffic stay cleanly separated.
The GPT pass running 30 days with $2350 of quota and $700 per week costs $81.53 for 30 days. Its quota is drawn at the duty-pass rate x2.5, which is at most about $940 of usage at list prices, and less on models whose pass rate sits above list. The larger GPT pass, 30 days with $5650 of quota and $1640 per week, costs $194.03 for 30 days, with up to $5650 of quota drawn at the duty-pass rate x2.5, at most about $2260 of usage at list prices, and less on models whose pass rate sits above list.
Two pass behaviours to keep in mind. A call already let through on a pass is drawn in full from the pass even if it runs past the quota or the 7-day ceiling, and that overrun counts against the earliest-expiring card. When a pass is nearly used up, each running call holds $3 x the draw rate, and an extra parallel call gets HTTP 429 until the running ones finish.
On the money side, a top-up can be refunded within 14 days: unused balance comes back minus what was consumed and the payment channel's fees. Bounty and promotional credit are not refundable. The referral bounty pays 18% at level 1 and 6% at level 2 of what referred members pay, and it can be withdrawn from $11.11 or moved into the wallet.
Tracing the shift from the Relay365 dashboard
Once traffic is moving, the dashboard becomes the handover tool of choice. Beyond the usage log of the latest 200 requests, it holds a ledger of wallet, bounty and pass accounts, so you can see which pot paid for which call without switching screens. Quick-wiring snippets sit next to the key list, which shortens the gap between creating a key and running the first request.
If anything looks off, in-site messages reach the desk directly; log in first, then write. The dashboard is available in six interface languages. Relay365 keeps every lane on one table, every request traceable in the usage log, and the four token types priced separately, so the next colleague on shift can pick up where you left off.
When you are ready, create your Relay365 account, claim the $0.25 signup credit, and send that first gpt-5.6-sol request. The duty desk will be on the other end of the log.
Further desk bulletins
| Date | Bulletin title | Filed under | Language |
|---|---|---|---|
| 2026-11-06 | GPT-6.1 Sol cURL smoke test on Relay365 API relay | Model watch | EN |
| 2026-10-31 | Qwen3.8 Max cURL smoke test on the Relay365 API relay | Model watch | EN |
| 2026-10-30 | Shift Note: Gemini Response Delivery, Two Clear Verdicts | Model watch | EN |
| 2026-10-30 | Shift Log: Two Models on the Support Queue | Model watch | EN |
| 2026-10-30 | Duty Log: When Claude Fable 5.1 Earns the Upgrade | Model watch | EN |
| 2026-10-30 | Shift log: Hunyuan 4 on Chinese support drafts | Model watch | EN |