GPT / Codex CLI Checks

GPT / Codex Gateway Candidate Checks

Use OpenAI's official API and Responses API behavior as the baseline. The providers below are candidates that support Codex CLI or OpenAI-compatible APIs; check 302.AI, OpenRouter and similar providers for base URLs, model names, pricing pages, privacy notes and update paths before testing GPT, Cursor, Cline, OpenAI SDK or LiteLLM workflows.

Quick answer

For Codex CLI, Cursor and OpenAI SDK workflows, the most important filter is OpenAI-compatible behavior: base URL, model names, streaming, error format, token billing, docs and privacy disclosures. 302.AI and OpenRouter-style providers should be checked against the same list.

What to verify before choosing

  • Does the provider expose an OpenAI-compatible `/v1` style API?
  • Are GPT, DeepSeek, Qwen, Gemini or other coding models documented?
  • Can you compare input and output token pricing from a public page before testing?
  • Can you test with non-sensitive code before routing a private repository?

Official API Baseline

Start here for production, sensitive code and compliance-heavy workflows. Third-party relays should be compared against these official routes, not treated as the default.

OpenAI

GPT, Codex-style workflows, OpenAI SDK and Responses API compatibility baseline.

Anthropic

Claude Code, Claude API and Anthropic-compatible behavior baseline.

Google AI Studio

Gemini API, multimodal model access and Google-native developer workflows.

DeepSeek

DeepSeek API, low-cost reasoning/code models and official OpenAI-compatible reference.

Gateway and Relay Candidates

After checking the official API baseline, compare provider type, suitable workflow, tool compatibility, public source links, missing fields and next actions in one compact table.

Entry Provider Type Fit Tool compatibility Public links Notes Source / action
Check 1 OpenRouter
openrouter.ai
Global aggregator Benchmarking model availability, pricing, and a global API gateway baseline.
Codex CLI Cursor Cline
Run low-balance test first
Details Website
Check 2 SiliconFlow
siliconflow.com
China model platform Low-cost DeepSeek, Qwen, embedding, image, and open model workloads.
Codex CLI Cursor Cline
Run low-balance test first
Details Website
Check 3 302.AI
302.ai
Global aggregator Users who want both AI tools and API access under one account, while still checking official docs, pricing and privacy links before production use.
Codex CLI Cursor Cline
Run low-balance test first
Details Website
Check 4 DMXAPI
dmxapi.com.cn
Enterprise gateway Companies that need private deployment, auditability, and a managed API control layer.
Codex CLI Cursor Cline
Docs need checkingPricing needs checking
Details Website
Check 5 MoleAPI
moleapi.com
Claude Code friendly Developers who want one endpoint for Claude Code, Cursor, Codex CLI, and common OpenAI SDK workflows.
Claude Code Codex CLI Cursor Cline
Run low-balance test first
Details Website
Check 6 API易
apiyi.com
Claude Code friendly Teams that care about documentation, invoices, and visible model/pricing references.
Claude Code Codex CLI Cursor Cline
Run low-balance test first
Details Website
Check 7 灵芽 API
api.lingyaai.cn
Claude Code friendly Users who primarily need copyable setup steps for AI coding terminals and editors.
Claude Code Codex CLI Cursor Cline
Run low-balance test first
Details Website
Check 8 柏拉图 AI
api.bltcy.ai
Claude Code friendly Users comparing Chinese relay services with coding-tool setup support.
Claude Code Codex CLI Cursor Cline
Pricing needs checking
Details Website

Use these checks this way

  1. Start with source links: official site, docs and pricing should be easy to verify.
  2. Use the public source checker when a provider page is missing docs, pricing, models, privacy, terms, status or support fields.
  3. Use official API routes as the baseline before treating any relay or gateway as a candidate.
  4. Treat missing docs, missing pricing and unclear compatibility as filtering signals.
  5. Open the provider detail page to see source fields and risk notes before deciding what to verify next.

Next pages to compare