AnyInt Docs
API Reference

Endpoint Index

Endpoint-first map of the public AnyInt gateway surface, including status, auth style, and the canonical docs page for each API family.

Use this page when you need to answer: "Which route should I call?" It is the endpoint-first companion to the product-oriented guides.

This page lists the public customer-facing contract. It does not list non-public operational routes, admin routes, debug endpoints, provider callback internals, or deployment-specific implementation details.

For machine-readable use, fetch:

GET https://anyint.ai/docs/api-endpoints.json

Status labels

StatusMeaning
StableDocumented public route for normal integrations
BetaAvailable route that should be verified in your target account before production use
Pass-throughCompatibility or provider route proxied to an upstream service; schema follows the upstream family where not documented locally
  1. Start with Models API to discover usable model IDs.
  2. Use OpenAI Compatible API for normal chat and streaming.
  3. Use OpenAI Responses API only for tools that specifically expect Responses API wiring.
  4. Use Anthropic Compatible API or Gemini Compatible API when your app needs provider-native payloads.
  5. Use Media APIs, Kling video, and AI Music API for asset workflows.
  6. Run the Verify Your Integration checklist before production launch.

Parameter detail

This endpoint index is intentionally compact. Use the linked API page for request parameter tables, response field tables, and full examples. Machine-readable route metadata is available in api-endpoints.json, but the human API page remains the source of truth for parameter meaning and customer guidance.

Core public routes

FamilyStatusAuthMain routesDocs
Models APIStableBearer or Anthropic headersGET /openai/v1/models, GET /anthropic/v1/modelsModels API
OpenAI-compatible chatStableBearerPOST /openai/v1/chat/completions, POST /openai/v1/completionsOpenAI Compatible API
OpenAI ResponsesBetaBearerPOST /openai/v1/responses, GET /openai/v1/responses/{response_id}OpenAI Responses API
Anthropic-compatibleStablex-api-key + anthropic-versionPOST /anthropic/v1/messages, POST /anthropic/v1/messages/count_tokensAnthropic Compatible API
Gemini-compatibleStableBearerPOST /gemini/v1beta/models/{model}:generateContent, POST /gemini/v1beta/models/{model}:streamGenerateContent?alt=sseGemini Compatible API
DashScope mediaStableBearerPOST /dashscope/v1/services/aigc/multimodal-generation/generation, POST /dashscope/v1/services/aigc/video-generation/video-synthesis, GET /dashscope/v1/tasks/{task_id}Media APIs
Transtreams KlingStableBearerPOST /transtreams/kling/v1/videos/text2video, GET /transtreams/kling/v1/videos/text2video/{task_id}, POST /transtreams/kling/v1/videos/image2video, GET /transtreams/kling/v1/videos/image2video/{task_id}, POST /transtreams/kling/v1/videos/omni-video, GET /transtreams/kling/v1/videos/omni-video/{task_id}Kling video
AI MusicStableBearerPOST /suno/generate, POST /suno/extend, GET /suno/query/task?taskId={task_id}AI Music API

Extended public routes

FamilyStatusUse whenDocs
OpenAI extended endpointsPass-throughYou need embeddings, image generation, audio, files, batches, assistants, threads, or OpenAI-style video routesOpenAI Extended Endpoints

What not to infer

Do not assume every upstream provider route is public just because a proxy route exists in the gateway. This public docs site documents only external integration surfaces. Prefer the explicitly documented route pages and verify provider-specific payloads in your account before production use.

Do not call unprefixed model routes such as GET /v1/models. The published model discovery routes are /openai/v1/models and /anthropic/v1/models.

Do not use AnyInt customer docs to infer any non-public APIs. Those surfaces are not part of the public gateway contract unless they are explicitly documented here.

On this page