E-larex's AI Proxy is an API gateway that aggregates access to various large language model providers. It offers a single interface for developers to interact with models from providers like OpenAI, Claude, Gemini, MoonshotAI, Zhipu, and over 30 others. The service provides standardized endpoints compatible with common API patterns, including chat completions, embeddings, image generation, and audio processing. Key endpoints include /v1/chat/completions, /v1/embeddings, /v1/images/generations, and /v1/audio/transcriptions. The platform emphasizes competitive pricing and stability without subscription requirements, allowing users to switch providers by modifying the base URL. It supports use cases such as chatbots, content generation, multimodal applications, and audio processing through a consolidated API layer.
E-larex's AI Proxy
ai.e-larex.com
E-larex AI Proxy provides unified access to multiple AI models through an OpenAI-compatible API gateway.
- Models
- 15 models
- From
- --
- Speed
- 27 tok/s
- Updated
- 6/8/2026
- Latency
- 0.00 s
- Created At
- 4/3/2026
- Recharge Rate
- ¥7.30 per $1 quota
Features
Login Methods
API Endpoints
- Endpoint 1Historical / Unverified
https://ai.e-larex.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 E-larex's AI Proxy
Health Check
API Benchmarks & Pricing
Compare 7 model rows across audit recency, latest speed tests, throughput, latency, and per-token pricing.
deepseek-v4-prodefault | $0.435/M | $0.870/M | - | - |
deepseek-v4-flashdefault | $0.140/M | $0.280/M | - | - |
mimo-v2.5-prodefault | $0.435/M | $0.870/M | - | - |
mimo-v2.5default | $0.140/M | $0.280/M | - | - |
kimi-k2.6default | $0.950/M | $4.00/M | - | - |
| - | - | 27.4 t/s | 3.83 s | |
kimi-k2.5default | $0.600/M | $3.00/M | - | - |
Showing 7 of 7 model rows
Recent Test Records
| Time | Model | Speed | Latency |
|---|---|---|---|
| Apr 3, 07:17 AM | glm-5.1 | 27.37 tok/s | 3.83s |
Similar API Provider Alternatives to Compare
Compare E-larex's AI Proxy alternatives against 6 nearby API providers using 138 LMSpeed signals across shared model coverage, pricing, benchmark speed, uptime, and free-model availability.
| Provider | Why compare | Models | Free | Avg price | Speed | 30d uptime |
|---|---|---|---|---|---|---|
| E-larex's AI Proxy ai-e-larex-com E-larex AI Proxy provides unified access to multiple AI models through an OpenAI-compatible API gateway. | Current provider baseline | 15 | 6 | N/A | 27 tok/s | 9970% |
| TommyLam API new-api-tommylam-me TommyLam API offers an OpenAI-compatible API gateway for accessing multiple AI models at competitive rates. |
| 231 | 100 | N/A | 61 tok/s | 10000% |
| 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% |
| 哈基米API站 api-gemai-cc 哈基米API站 offers a unified API gateway for large language models with competitive pricing and stable service. |
| 323 | 0 | $0.930/M | 119 tok/s | 9980% |
| 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% |
| Privnode privnode Privnode appears to provide an OpenAI-compatible API endpoint on privnode.com. The public root is protected by a Cloudflare challenge during review. |
| 92 | 28 | N/A | 36 tok/s | 0% |
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.