Introduction
SmartAPI is a unified API gateway that gives you access to leading large language models through OpenAI-compatible, OpenAI Responses, and Anthropic-compatible endpoints. Point your existing SDKs at SmartAPI, swap in your SmartAPI key, and start sending requests — no rewrites required.
Why SmartAPI#
- Drop-in compatible. Reuse the official OpenAI and Anthropic SDKs. Only the base URL and API key change.
- One key, many models. A single SmartAPI key can call any listed model across providers.
- Built-in routing & failover. Requests are routed to healthy upstream channels automatically, with retries on transient upstream errors.
- Usage-based billing. All usage is charged in credits ($1 = 100 credits). Chat models are billed by tokens; image/video by generation — all priced per model.
Base URL#
All API requests are sent to the OpenAPI gateway:
https://api.smartapi.cc/api/openapi/v1| Endpoint | Protocol | Path |
|---|---|---|
| Chat Completions | OpenAI-compatible | POST /chat/completions |
| Responses | OpenAI Responses | POST /responses |
| Messages | Anthropic-compatible | POST /messages |
| Image Generation | SmartAPI | POST /generate/image/generations |
| Video Generation | SmartAPI | POST /generate/video/tasks |
SmartAPI is a transparent proxy: request and response bodies follow the upstream provider’s specification. If you already know the OpenAI or Anthropic API, you already know SmartAPI.
How it works#
- Create an API key in the console.
- Choose a model from the model list.
- Send a request to the matching endpoint with your key.
Your request hits the SmartAPI OpenAPI gateway, which authenticates the key, checks your balance and rate limits, routes to a healthy upstream channel (with automatic failover), and streams the response straight back to you.
Next steps#
- Quickstart — make your first request in minutes.
- Authentication — how API keys work.
- Chat Completions — the OpenAI-compatible endpoint.
- Responses — the OpenAI Responses protocol (
openai-response). - Messages — the Anthropic-compatible endpoint.
- Image Generation — the synchronous image endpoint.
- Video Generation — the asynchronous video task endpoint.