GPT
Check the advertised GPT route, not just its label.
AI Ranking / Data snapshot
Compare AI API services with transparent scores, public evidence and practical buying guides. Build a shortlist, understand the gaps, then test what matters to you.
Page 01
| Rank | Provider & evidence | Data score | Reported uptime | Reported latency | Models | Reviews | Policies | View source |
|---|---|---|---|---|---|---|---|---|
| 1 | ToTokens ToTokens: Public-data score 74.9, with 100% weighted field coverage. Reported uptime: 99.1%; reported latency: 4.8 s. Provider profile → | 74.9Coverage 100% | 99.1% | 4.8 s | 33 | 4 / 5 (8) | Refund: YesInvoice: Yes | ↗ |
| 2 | 云渡 云渡: Public-data score 79.1, with 100% weighted field coverage. Reported uptime: 100%; reported latency: 3.4 s. Provider profile → | 79.1Coverage 100% | 100% | 3.4 s | 30 | 5 / 5 (4) | Refund: YesInvoice: Yes | ↗ |
| 3 | 速蹬 速蹬: Public-data score 75, with 85% weighted field coverage. Reported uptime: 100%; reported latency: 4.4 s. Provider profile → | 75Coverage 85% | 100% | 4.4 s | 22 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 4 | 88API Token聚合平台 88API Token聚合平台: Public-data score 65.1, with 100% weighted field coverage. Reported uptime: 96.1%; reported latency: 5.6 s. Provider profile → | 65.1Coverage 100% | 96.1% | 5.6 s | 68 | 5 / 5 (2) | Refund: NoInvoice: Yes | ↗ |
| 5 | hao.ai hao.ai: Public-data score 52.5, with 100% weighted field coverage. Reported uptime: 76%; reported latency: 3.4 s. Provider profile → | 52.5Coverage 100% | 76% | 3.4 s | 19 | 5 / 5 (3) | Refund: YesInvoice: Yes | ↗ |
| 6 | 灵算 灵算: Public-data score 76.3, with 100% weighted field coverage. Reported uptime: 99.7%; reported latency: 5.4 s. Provider profile → | 76.3Coverage 100% | 99.7% | 5.4 s | 34 | 4.4 / 5 (14) | Refund: YesInvoice: Yes | ↗ |
| 7 | 灵珑AI 灵珑AI: Public-data score 74.7, with 85% weighted field coverage. Reported uptime: 100%; reported latency: 4.6 s. Provider profile → | 74.7Coverage 85% | 100% | 4.6 s | 44 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 8 | 9527code 9527code: Public-data score 71.9, with 100% weighted field coverage. Reported uptime: 93.9%; reported latency: 5.7 s. Provider profile → | 71.9Coverage 100% | 93.9% | 5.7 s | 65 | 4.9 / 5 (60) | Refund: YesInvoice: Yes | ↗ |
| 9 | SudoCode SudoCode: Public-data score 62.9, with 100% weighted field coverage. Reported uptime: 88.9%; reported latency: 4.3 s. Provider profile → | 62.9Coverage 100% | 88.9% | 4.3 s | 24 | 4.8 / 5 (9) | Refund: YesInvoice: Yes | ↗ |
| 10 | 破晓 破晓: Public-data score 41.3, with 80% weighted field coverage. Reported uptime: 77.1%; reported latency: 6.9 s. Provider profile → | 41.3Coverage 80% | 77.1% | 6.9 s | 29 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 11 | ToolCode ToolCode: Public-data score 76.2, with 100% weighted field coverage. Reported uptime: 100%; reported latency: 4 s. Provider profile → | 76.2Coverage 100% | 100% | 4 s | 19 | 5 / 5 (1) | Refund: YesInvoice: Yes | ↗ |
| 12 | Modelflare Modelflare: Public-data score 70.4, with 100% weighted field coverage. Reported uptime: 97.6%; reported latency: 5.4 s. Provider profile → | 70.4Coverage 100% | 97.6% | 5.4 s | 47 | 3.3 / 5 (20) | Refund: YesInvoice: Yes | ↗ |
| 13 | ZNB.ai ZNB.ai: Public-data score 63.8, with 100% weighted field coverage. Reported uptime: 97.4%; reported latency: 7.8 s. Provider profile → | 63.8Coverage 100% | 97.4% | 7.8 s | 34 | 5 / 5 (1) | Refund: YesInvoice: No | ↗ |
| 14 | BuyToken BuyToken: Public-data score 63.8, with 100% weighted field coverage. Reported uptime: 90.6%; reported latency: 6 s. Provider profile → | 63.8Coverage 100% | 90.6% | 6 s | 30 | 5 / 5 (1) | Refund: YesInvoice: Yes | ↗ |
| 15 | FluxToken FluxToken: Public-data score 58.3, with 85% weighted field coverage. Reported uptime: 89.1%; reported latency: 6.6 s. Provider profile → | 58.3Coverage 85% | 89.1% | 6.6 s | 45 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 16 | 悟空API 悟空API: Public-data score 64.8, with 100% weighted field coverage. Reported uptime: 94%; reported latency: 6.1 s. Provider profile → | 64.8Coverage 100% | 94% | 6.1 s | 30 | 4.2 / 5 (9) | Refund: YesInvoice: Yes | ↗ |
| 17 | Yomi API Yomi API: Public-data score 54.8, with 85% weighted field coverage. Reported uptime: 87.1%; reported latency: 6.3 s. Provider profile → | 54.8Coverage 85% | 87.1% | 6.3 s | 45 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 18 | OmniaKey OmniaKey: Public-data score 65.8, with 85% weighted field coverage. Reported uptime: 92.6%; reported latency: 5.5 s. Provider profile → | 65.8Coverage 85% | 92.6% | 5.5 s | 244 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 19 | ccgo ccgo: Public-data score 72.2, with 100% weighted field coverage. Reported uptime: 98.7%; reported latency: 5.6 s. Provider profile → | 72.2Coverage 100% | 98.7% | 5.6 s | 30 | 5 / 5 (1) | Refund: YesInvoice: Yes | ↗ |
| 20 | 吉吉不降智AI 吉吉不降智AI: Public-data score 69.2, with 85% weighted field coverage. Reported uptime: 96.2%; reported latency: 6.1 s. Provider profile → | 69.2Coverage 85% | 96.2% | 6.1 s | 44 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 21 | Toknex Toknex: Public-data score 75.4, with 100% weighted field coverage. Reported uptime: 100%; reported latency: 4.8 s. Provider profile → | 75.4Coverage 100% | 100% | 4.8 s | 24 | 5 / 5 (4) | Refund: YesInvoice: Yes | ↗ |
| 22 | 词元玩家 词元玩家: Public-data score 73.6, with 80% weighted field coverage. Reported uptime: 100%; reported latency: 2.3 s. Provider profile → | 73.6Coverage 80% | 100% | 2.3 s | 7 | Not recorded | Refund: Not recordedInvoice: Yes | ↗ |
| 23 | 词易 词易: Public-data score 59.3, with 100% weighted field coverage. Reported uptime: 87.3%; reported latency: 5.9 s. Provider profile → | 59.3Coverage 100% | 87.3% | 5.9 s | 41 | 4.4 / 5 (7) | Refund: YesInvoice: Yes | ↗ |
| 24 | PackyCode PackyCode: Public-data score 68.8, with 85% weighted field coverage. Reported uptime: 98.3%; reported latency: 5.8 s. Provider profile → | 68.8Coverage 85% | 98.3% | 5.8 s | 65 | 3.5 / 5 (4) | Refund: Not recordedInvoice: Not recorded | ↗ |
| 25 | Framefly Framefly: Public-data score 67.2, with 100% weighted field coverage. Reported uptime: 99.2%; reported latency: 4.3 s. Provider profile → | 67.2Coverage 100% | 99.2% | 4.3 s | 11 | 5 / 5 (1) | Refund: NoInvoice: Yes | ↗ |
| 26 | ModCon ModCon: Public-data score 70.2, with 95% weighted field coverage. Reported uptime: 99.4%; reported latency: 5 s. Provider profile → | 70.2Coverage 95% | 99.4% | 5 s | 15 | 5 / 5 (3) | Refund: YesInvoice: Not recorded | ↗ |
| 27 | iKunAPI iKunAPI: Public-data score 69.6, with 85% weighted field coverage. Reported uptime: 99.5%; reported latency: 4.1 s. Provider profile → | 69.6Coverage 85% | 99.5% | 4.1 s | 5 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 28 | sudocode.us sudocode.us: Public-data score 74.4, with 85% weighted field coverage. Reported uptime: 99.3%; reported latency: 4.9 s. Provider profile → | 74.4Coverage 85% | 99.3% | 4.9 s | 61 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 29 | SevnX SevnX: Public-data score 70, with 95% weighted field coverage. Reported uptime: 99.7%; reported latency: 4.6 s. Provider profile → | 70Coverage 95% | 99.7% | 4.6 s | 12 | 5 / 5 (5) | Refund: Not recordedInvoice: Yes | ↗ |
| 30 | 8sToken 8sToken: Public-data score 77, with 100% weighted field coverage. Reported uptime: 98.6%; reported latency: 4.7 s. Provider profile → | 77Coverage 100% | 98.6% | 4.7 s | 77 | 5 / 5 (9) | Refund: YesInvoice: Yes | ↗ |
| 31 | 云舟AI 云舟AI: Public-data score 67.9, with 85% weighted field coverage. Reported uptime: 100%; reported latency: 4.9 s. Provider profile → | 67.9Coverage 85% | 100% | 4.9 s | 3 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 32 | RunAPI RunAPI: Public-data score 73.5, with 85% weighted field coverage. Reported uptime: 97.7%; reported latency: 5.8 s. Provider profile → | 73.5Coverage 85% | 97.7% | 5.8 s | 136 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 33 | SvenX SvenX: Public-data score 67.5, with 85% weighted field coverage. Reported uptime: 94.9%; reported latency: 4.1 s. Provider profile → | 67.5Coverage 85% | 94.9% | 4.1 s | 19 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 34 | aiaimark aiaimark: Public-data score 45.2, with 100% weighted field coverage. Reported uptime: 69.3%; reported latency: 4 s. Provider profile → | 45.2Coverage 100% | 69.3% | 4 s | 42 | 5 / 5 (2) | Refund: YesInvoice: No | ↗ |
| 35 | sidrune sidrune: Public-data score 45.6, with 85% weighted field coverage. Reported uptime: 82.1%; reported latency: 7.4 s. Provider profile → | 45.6Coverage 85% | 82.1% | 7.4 s | 59 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 36 | jcode jcode: Public-data score 56.5, with 85% weighted field coverage. Reported uptime: 93.1%; reported latency: 5.9 s. Provider profile → | 56.5Coverage 85% | 93.1% | 5.9 s | 26 | Not recorded | Refund: YesInvoice: No | ↗ |
| 37 | 灵途 灵途: Public-data score 64.6, with 80% weighted field coverage. Reported uptime: 95.5%; reported latency: 6.1 s. Provider profile → | 64.6Coverage 80% | 95.5% | 6.1 s | 41 | Not recorded | Refund: Not recordedInvoice: Yes | ↗ |
| 38 | FlyRouter FlyRouter: Public-data score 73.7, with 85% weighted field coverage. Reported uptime: 99.5%; reported latency: 4.4 s. Provider profile → | 73.7Coverage 85% | 99.5% | 4.4 s | 47 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 39 | onepay onepay: Public-data score 62.8, with 80% weighted field coverage. Reported uptime: 94.3%; reported latency: 6 s. Provider profile → | 62.8Coverage 80% | 94.3% | 6 s | 43 | Not recorded | Refund: Not recordedInvoice: Yes | ↗ |
| 40 | SaTuoAPI SaTuoAPI: Public-data score 63.8, with 100% weighted field coverage. Reported uptime: 96.4%; reported latency: 6.7 s. Provider profile → | 63.8Coverage 100% | 96.4% | 6.7 s | 39 | 5 / 5 (1) | Refund: NoInvoice: Yes | ↗ |
Model index
These are keyword-based research shortlists, not verified compatibility lists. Check the exact model ID, protocol and account limits before paying.
Check the advertised GPT route, not just its label.
Check Claude-specific behavior in your intended integration.
Clarify what the provider means by Codex access.
Validate the Gemini request types you actually need.
Distinguish DeepSeek model claims from deployment details.
Check the GLM version and deployment arrangement.
Identify the specific Qwen variant behind the listing.
Verify Kimi claims against complete requests.
AI Ranking
AI Ranking is a public-data index, not a laboratory benchmark. Use its listings to build a shortlist, identify missing information, and prepare your own checks. A high position does not establish model quality, security, or suitability for your workload.
Prioritize a low spending limit, understandable documentation, and easy key revocation. Test one representative request before funding an account.
Check streaming, peak-hour errors, and time to the first useful response. A published latency figure cannot describe the whole user experience.
Require written data-handling terms, operational contacts, and a tested fallback. Treat purchasing, privacy, and technical acceptance as separate decisions.
Guides
Turn directory signals into questions, controlled trials, and explicit acceptance criteria.
Build a shortlist around evidence for your workload, not catalogue size or position alone.
Read the guide →Translate token rates, account credits, and failed attempts into a budget you can reconcile.
Read the guide →Make failure, privacy, and recovery measurable parts of acceptance, not follow-up work.
Read the guide →No. The index organizes public records; its score is not an independent performance benchmark or a security assessment.
No. The score combines listing signals, not task accuracy. Evaluate output quality with examples and acceptance criteria relevant to your application.
Not necessarily. Records are snapshots with an unknown measurement window; regions, request types, and collection methods may differ.
No. Topics use keyword matches, not capability verification. Confirm exact models, versions, features, and access restrictions with the operator.
No. Missing signals are omitted from the weighted mean and reduce coverage. They remain questions to investigate, not proof of failure.
Only as a lead. Obtain the current written terms, applicable legal entity, eligibility conditions, and any deadlines before paying.