GPT and Codex API Relay Recommendations and Route Pricing
Choose a GPT or Codex model and route class to compare official input and output prices with model-level API verification.
Recommendation requirements
A provider must publish a price for the selected model and pass that exact model on our test account before entering the verified shortlist.
No blended estimate
Input and output rates are compared separately for the same model and route class instead of being hidden inside an estimated blended price.
Same-model price and paid API evidence
Six provider profiles: compare input and output rates for the same model, then inspect the actual request outcomes. Live rankings and subscription estimates may differ from this build-time snapshot.
GPT-5.6 Sol · premium routes
| Provider | Price group | Input / 1M | Output / 1M | Source date | API passed / total | Latest test | P50 total | Best suited for |
|---|---|---|---|---|---|---|---|---|
| H API | GPT Pro | ¥1.5 | ¥9 | 2026-09-25 | 3 / 3 | 2026-09-27 | 3.14 s | Codex or Responses API workloads after protocol testing |
| APINebula | CODEX | ¥1.95 | ¥11.7 | 2026-09-25 | No sample | - | - | Codex or Responses API workloads after protocol testing |
| UU API | Codex-GPT Pro account pool | ¥2 | ¥12 | 2026-09-25 | 3 / 3 | 2026-09-25 | 1.83 s | Codex or Responses API workloads after protocol testing |
| boxying | Codex premium pool | ¥2.2 | ¥13.2 | 2026-09-25 | 3 / 3 | 2026-09-25 | 10.8 s | Codex or Responses API workloads after protocol testing |
| LinksAPI | GPT Pro (Codex included), 0.3x | ¥3.25 | ¥26 | 2026-09-25 | 3 / 3 | 2026-09-27 | 17.0 s | Codex or Responses API workloads after protocol testing |
| OpenOx | Pro direct route | ¥9 | ¥54 | 2026-09-24 | 4 / 4 | 2026-09-29 | 2.73 s | Codex or Responses API workloads after protocol testing |
Prices are provider-published pay-as-you-go rates, not subscription equivalents or reconciled charges. API samples cover the named model, but the test key's actual upstream group is not consistently recorded and may differ from the quoted group. P50 is successful end-to-end response time, not time to first token. A completed call does not prove model identity.
Frequently asked questions
How should I choose a GPT or Codex API relay?
Fix the exact GPT model and route class first, then compare separate input and output rates, paid request samples, response time, protocol compatibility, and billing evidence. A cheap client-only Codex pool should not be ranked as a general OpenAI API route.
Can a Codex key be used with every OpenAI-compatible client?
Not necessarily. Some routes support only the Responses API or a designated Codex client, while others expose Chat Completions or a broader OpenAI-compatible interface. Test the protocol you actually need.
Why can a listed GPT model still fail?
Model discovery and generation may use different permissions, groups, upstreams, or rate limits. AI Relay Check counts a model as verified only after an actual generation request succeeds.
Answer summary
- Latest test date
- Providers covered
- 6
- Models / protocols
- gpt-5.5 / gpt-5.6-sol / gpt-5.6-terra +1 more · OpenAI / Responses
- Successful / total samples
- 108 / 121
- Price / billing verified
- 6/6 price · 5/6 billing
- Still unverified
- Model identity, every Codex client feature, future uptime and unmatched billing
- One-sentence conclusion
- A GPT or Responses success verifies that dated request only; confirm the exact Codex client, route group and billing rule before buying.