Jey-API is a subscription-based API conversion platform that aggregates access to multiple AI models. It offers a single API key to call connected models like Claude, GPT, Gemini, and Antigravity, eliminating the need for separate applications. The platform features smart routing across multiple upstream accounts with automatic failover for reliability. Billing is pay-as-you-go with usage-based pricing and quota limits, providing visibility into team consumption. Key capabilities include session persistence and one-click access to supported AI models.
Jey-API
openai.zidianidc.com
Jey-API provides API conversion and unified access to multiple AI models through OpenAI-compatible endpoints.
- Models
- 1 models
- From
- --
- Speed
- 55 tok/s
- Updated
- 6/8/2026
- Latency
- 0.00 s
- Created At
- 3/26/2026
API Endpoints
- Endpoint 1
openai.zidianidc.com
Claim this provider
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 Jey-API
Health Check
100%Recent availability
History (72 pts)
PastNow
API Benchmarks & Pricing
Compare 1 model rows across audit recency, latest speed tests, throughput, latency, and per-token pricing.
| 54.9 t/s | 3.53 s |
Showing 1 of 1 model rows
Recent Test Records
| Time | Model | Speed | Latency |
|---|---|---|---|
| Mar 26, 12:13 AM | gpt-5.4 | 54.94 tok/s | 3.53s |
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.