About APIArc

Overview

APIArc is a multi-provider AI gateway for developers. One account, prepaid balance, API key, and base URL provide access to model families from OpenAI, Anthropic, Google, DeepSeek, Moonshot AI, Zhipu AI, ByteDance, and other providers. APIArc says requests use official provider channels and that applications can switch models by changing the model identifier.

API compatibility

The documented base URL is https://api.apiarc.dev. APIArc supports OpenAI-compatible Chat Completions and Responses endpoints, the Anthropic Messages protocol, streaming with Server-Sent Events, and a models endpoint. Existing OpenAI clients can connect by changing the base URL, API key, and model ID.

Models and billing

The catalog includes text, reasoning, multimodal, image, and video models. Billing is usage-based through prepaid credits, with model pricing and technical limits shown in the APIArc catalog. Model availability, routing, capabilities, and prices can change, so production users should confirm the current catalog and test a fallback model.

Data handling and support

According to the APIArc privacy policy, the standard gateway does not persist prompts, input files, or model outputs after a request completes and does not use that content for training. The selected upstream provider still processes the request under its own policies. Documentation is available at https://apiarc.ai/docs, and support can be reached at [email protected].

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.

APIArc

Billing

API Endpoints

Contact

Leaderboard Rankings