Choose a provider you can verify
Build a shortlist around evidence for your workload, not catalogue size or position alone.
Read the guide →AI Ranking / DeepSeek
Distinguish DeepSeek model claims from deployment details.
Page 01
| Rank | Provider & evidence | Data score | Reported uptime | Reported latency | Models | Reviews | Policies | View source |
|---|---|---|---|---|---|---|---|---|
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 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 | ↗ |
| 41 | tongbatokens tongbatokens: Public-data score 58.8, with 80% weighted field coverage. Reported uptime: 94.6%; reported latency: 5.7 s. Provider profile → | 58.8Coverage 80% | 94.6% | 5.7 s | 29 | Not recorded | Refund: Not recordedInvoice: Yes | ↗ |
| 42 | CheapRouter CheapRouter: Public-data score 64.4, with 85% weighted field coverage. Reported uptime: 94.8%; reported latency: 6.8 s. Provider profile → | 64.4Coverage 85% | 94.8% | 6.8 s | 32 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 43 | 天才程序员 天才程序员: Public-data score 54.6, with 85% weighted field coverage. Reported uptime: 90.4%; reported latency: 5.1 s. Provider profile → | 54.6Coverage 85% | 90.4% | 5.1 s | 33 | Not recorded | Refund: YesInvoice: No | ↗ |
| 44 | 林易API · linyiapi.ai 林易API · linyiapi.ai: Public-data score 63.9, with 100% weighted field coverage. Reported uptime: 94.3%; reported latency: 6.1 s. Provider profile → | 63.9Coverage 100% | 94.3% | 6.1 s | 10 | 5 / 5 (1) | Refund: YesInvoice: Yes | ↗ |
| 45 | 天枢云阙中转站 天枢云阙中转站: Public-data score 62.4, with 85% weighted field coverage. Reported uptime: 97.2%; reported latency: 6.8 s. Provider profile → | 62.4Coverage 85% | 97.2% | 6.8 s | 22 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 46 | GGAPI GGAPI: Public-data score 58, with 75% weighted field coverage. Reported uptime: 97%; reported latency: 5.1 s. Provider profile → | 58Coverage 75% | 97% | 5.1 s | 6 | Not recorded | Refund: Not recordedInvoice: Not recorded | ↗ |
| 48 | Moe Api Moe Api: Public-data score 69, with 100% weighted field coverage. Reported uptime: 98.3%; reported latency: 8 s. Provider profile → | 69Coverage 100% | 98.3% | 8 s | 44 | 4 / 5 (1) | Refund: YesInvoice: Yes | ↗ |
| 49 | Moniker Moniker: Public-data score 52.6, with 85% weighted field coverage. Reported uptime: 86.7%; reported latency: 5.6 s. Provider profile → | 52.6Coverage 85% | 86.7% | 5.6 s | 64 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 50 | LinoRoute LinoRoute: Public-data score 65.5, with 100% weighted field coverage. Reported uptime: 99.7%; reported latency: 8 s. Provider profile → | 65.5Coverage 100% | 99.7% | 8 s | 166 | 5 / 5 (1) | Refund: YesInvoice: No | ↗ |
| 51 | 银河算力实验室 银河算力实验室: Public-data score 76.8, with 100% weighted field coverage. Reported uptime: 100%; reported latency: 3 s. Provider profile → | 76.8Coverage 100% | 100% | 3 s | 26 | 5 / 5 (5) | Refund: YesInvoice: Yes | ↗ |
| 52 | XycAi(星道智能) XycAi(星道智能): Public-data score 46, with 95% weighted field coverage. Reported uptime: 66.2%; reported latency: 3.7 s. Provider profile → | 46Coverage 95% | 66.2% | 3.7 s | 132 | 5 / 5 (1) | Refund: NoInvoice: Yes | ↗ |
| 53 | Logits Token Logits Token: Public-data score 60.7, with 85% weighted field coverage. Reported uptime: 92.4%; reported latency: 6.7 s. Provider profile → | 60.7Coverage 85% | 92.4% | 6.7 s | 37 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 55 | GPTEAM GPTEAM: Public-data score 56.8, with 85% weighted field coverage. Reported uptime: 88.7%; reported latency: 7.7 s. Provider profile → | 56.8Coverage 85% | 88.7% | 7.7 s | 68 | Not recorded | Refund: YesInvoice: Yes | ↗ |
| 57 | 橙子AI 橙子AI: Public-data score 68.7, with 85% weighted field coverage. Reported uptime: 99.8%; reported latency: 6.7 s. Provider profile → | 68.7Coverage 85% | 99.8% | 6.7 s | 46 | Not recorded | Refund: YesInvoice: Yes | ↗ |
These are keyword-based research shortlists, not verified compatibility lists. Check the exact model ID, protocol and account limits before paying.
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 →