Overview
This section explains the main API families behind https://gateway.api.anyint.ai and links to the endpoint-first route map.
This section explains the main API families behind https://gateway.api.anyint.ai. The most important distinction is that AnyInt exposes more than one compatibility family. Some routes are OpenAI-style, some are Anthropic-style, some are Gemini-native, and media and music workflows are task-oriented.
If you need a route-by-route map, start with Endpoint Index. LLMs and integration tools can also fetch https://anyint.ai/docs/api-endpoints.json.
This section documents the public customer-facing gateway contract. It intentionally excludes non-public operational routes, admin routes, debug endpoints, deployment details, and provider callback internals.
Current endpoint families
| Family | Status | Routes | Best for |
|---|---|---|---|
| Models API | Stable | /openai/v1/models, /anthropic/v1/models | Discovering available models |
| OpenAI-compatible | Stable | /openai/v1/chat/completions | Existing OpenAI SDK clients |
| OpenAI Responses | Beta | /openai/v1/responses | Agent tools that require Responses API |
| Anthropic-compatible | Stable | /anthropic/v1/messages, /anthropic/v1/messages/count_tokens | Claude-style clients and token counting |
| Gemini-compatible | Stable | ...generateContent, ...streamGenerateContent | Gemini-native request shapes |
| Media APIs | Stable | DashScope and Transtreams Kling routes | Image and video generation |
| AI Music | Stable | /suno/* | Music generation and async media workflows |
Authentication patterns
The published routes currently use two header styles depending on the family:
- Bearer auth:
Authorization: Bearer <API_KEY> - Provider-style auth:
x-api-key: <API_KEY>with any required compatibility headers such asanthropic-version
Use the header convention documented on the page for the endpoint family you are integrating.
Recommended integration order
- Call Models API before shipping a hardcoded model ID.
- Start with OpenAI Compatible API if you only need chat or streaming.
- Use OpenAI Responses API only when a client expects Responses API wiring.
- Switch to Anthropic Compatible API or Gemini Compatible API when you need a provider-native request body.
- Use Media API, Kling video, and AI Music API for asset-generation workflows that are not plain chat completions.
- Run Verify Your Integration before production launch.
Async vs synchronous routes
Synchronous or stream-first
- OpenAI-compatible chat
- Anthropic messages
- Gemini text and image generation
- DashScope image generation
Task-based
- DashScope video generation
- All AI Music workflows
- Kling video tasks
Task-based APIs usually return a task ID first. You then poll a query endpoint or receive a webhook callback. Do not treat the initial 200 response as the final asset.
A practical rule for choosing an API family
Use the OpenAI-compatible route if:
- you want the quickest first integration
- your app already uses the OpenAI SDK
- you do not need provider-native request fields
Use provider-native routes if:
- you need Anthropic content blocks or token counting
- you need Gemini
generateContent,streamGenerateContent, orfunctionDeclarations - you want to mirror the provider's native request format inside your own product
Use media or music routes if:
- the output is an image, video, or song rather than a plain text response
- the workflow is naturally asynchronous
- you need task polling or webhook callbacks