TokenX24 is an API gateway that simplifies access to multiple AI models through a single API key. It offers smart routing across upstream accounts with automatic failover for reliability. The platform supports models including Claude, GPT, Gemini, and Antigravity, with more models planned. Features include session persistence, pay-as-you-go billing with quota limits, and team consumption visibility. Typical use cases include developers needing to integrate multiple AI models without managing separate API keys or handling routing logic.
TokenX24
tokenx24.com
TokenX24 provides a unified API gateway for accessing multiple AI models with smart routing, session persistence, and usage-based billing.
- Models
- 64 models
- From
- --
- Speed
- 51 tok/s
- Updated
- 7/31/2026
- Latency
- 0.00 s
- Created At
- 4/12/2026
API Endpoints
- Endpoint 1
tokenx24.com
Verify ownership to unlock provider management features:
- Edit provider name, content, and links
- Get featured with priority traffic and visibility boost
- Display a verified badge to build user trust
Leaderboard Rankings
Rankings are based on community-submitted tests and periodic health probes. Advisory only, not official data.
About TokenX24
Health Check
API Benchmarks & Pricing
Compare 64 model rows across audit recency, latest speed tests, throughput, latency, and per-token pricing.
codex-auto-review | ||||||||||
gpt-5.5 | ||||||||||
gpt-5.6-luna | ||||||||||
gpt-5.6-sol | ||||||||||
gpt-5.6-terra | ||||||||||
gpt-image-1 | ||||||||||
gpt-image-1.5 | ||||||||||
gpt-image-2 | ||||||||||
chatgpt-4o-latest | ||||||||||
gpt-3.5-turbo | ||||||||||
gpt-3.5-turbo-0125 | ||||||||||
gpt-3.5-turbo-1106 | ||||||||||
gpt-3.5-turbo-16k | ||||||||||
gpt-4 | ||||||||||
gpt-4-turbo | ||||||||||
gpt-4-turbo-preview | ||||||||||
gpt-4.1 | ||||||||||
gpt-4.1-mini | ||||||||||
gpt-4.1-nano | ||||||||||
gpt-4.5-preview | ||||||||||
gpt-4o | ||||||||||
gpt-4o-2024-08-06 | ||||||||||
gpt-4o-2024-11-20 | ||||||||||
gpt-4o-audio-preview | ||||||||||
gpt-4o-mini |
Showing 25 of 64 model rows
Recent Test Records
| Time | Model | Speed | Latency |
|---|---|---|---|
| Apr 12, 10:20 AM | gpt-5.4 | 50.58 tok/s | 1.46s |
Similar API Provider Alternatives to Compare
Compare TokenX24 alternatives against 6 nearby API providers using 300 LMSpeed signals across shared model coverage, pricing, benchmark speed, uptime, and free-model availability.
| Provider | Why compare | Models | Free | Avg price | Speed | 30d uptime |
|---|---|---|---|---|---|---|
| TokenX24 tokenx24-com TokenX24 provides a unified API gateway for accessing multiple AI models with smart routing, session persistence, and usage-based billing. | Current provider baseline | 64 | 0 | N/A | 51 tok/s | 9860% |
| ChooseC API ipv4-beta-lm-studio ChooseC API is a unified AI model aggregation gateway supporting 260+ mainstream models including Claude, GPT, Qwen, DeepSeek, Kimi, and GLM with OpenAI, Claude, and Gemini compatibility. |
| 335 | 9 | $0.095/M | 138 tok/s | 9950% |
| F2API api-f2api-com F2API is an enterprise AI gateway providing a unified OpenAI-compatible interface for accessing multiple large language models. |
| 1,262 | 0 | N/A | 272 tok/s | 9990% |
| Koyeb AI Gateway new-api-koyeb-app An OpenAI-compatible API gateway deployed on Koyeb, providing access to multiple AI models. |
| 578 | 420 | N/A | 33 tok/s | 9960% |
| DeadlySignal API deadlysignal |
| 290 | 0 | N/A | 63 tok/s | 9960% |
| ChooseC API ipv4-beta-kxcym-top-3001 ChooseC API is an OpenAI-compatible relay service hosted at ipv4-beta.kxcym.top, providing access to multiple AI models through standardized endpoints. |
| 122 | 9 | $0.095/M | 51 tok/s | 0% |
| PackyAPI codex-api-packycode-com PackyAPI (codex-api.packycode.com) is an OpenAI-compatible API relay for Codex and other models via a single interface. |
| 78 | 0 | $0.041/M | 69 tok/s | 9980% |
Notes
- Health checks: Scope: the 72-hour chart and recent availability measure API connectivity only. Each bar summarizes one hour of checks. Targets: LMSpeed tries the configured health check URL and provider status URL first, then API endpoints derived from known API hosts and recent speed-test base URLs. A website host is considered only when it looks like an API endpoint. Probe steps: each candidate goes through DNS lookup, TCP connection, TLS handshake for HTTPS, and an HTTP HEAD request with redirects followed. Probing stops after the first reachable candidate. Reachable criteria: every required network step must succeed. An HTTP response below 500 is treated as reachable, including 401 because it confirms that an authenticated API endpoint responded, except for statuses classified as blocked. Blocked results: HTTP 403, 429, 521, 525, and 530, plus detected WAF or Cloudflare challenges, are shown as blocked and excluded from availability calculations because LMSpeed cannot determine whether the API itself is down. Model availability: when a dedicated test key is configured, LMSpeed sends an authenticated GET request to a derived /models endpoint and compares returned model IDs with this provider's listed models. These per-model results appear in Models & Pricing and are not included in the provider connectivity percentage. Timeouts: TCP connection, TLS handshake, HTTP connectivity, and model requests each use a 20-second timeout. A full run can take longer when several candidates are tried. Frequency: a background worker checks all providers every 5 minutes by default. The 72-hour chart combines those samples into hourly bars, and the schedule may be changed by the service operator. Limit: automated samples are not an SLA and do not guarantee account quota, every model, every region, or successful completion requests. Check the provider's own status page before making operational decisions.
- Domain Rating data is sourced from Ahrefs. It is a 0–100 backlink-based domain strength signal and does not measure API speed or reliability.
- Announcements and FAQ are read from this provider's NewAPI status snapshot when available. LMSpeed stores the original content and optional English translations from the provider status source, then shows the localized fields on this page.

