Available now through the Anthropic Messages endpoint, with an OpenAI-compatible route for existing team tooling.
- Endpoint
- /v1/messages
- Status
- Available
- Billing
- Token
Integration guide for the Infwave unified gateway: available models, quick start, endpoints, code examples, SDK setup, and FAQ.
Unified view of Claude, ChatGPT, Gemini, DeepSeek, and visual model endpoints, model ID lookup, and status. Full catalog on the models page.
Available now through the Anthropic Messages endpoint, with an OpenAI-compatible route for existing team tooling.
Enablement returns the available model IDs. Useful for OpenAI SDK, Cursor, Codex CLI, and LangChain migration flows.
Routed through the OpenAI-compatible entrypoint. Exact model IDs are governed by the console and /v1/models.
For cost-sensitive and reasoning workloads. Public copy stays stable; callable aliases come from the live model API.
Video generation runs as async jobs with the same API key, job polling, and usage-log task details.
doubao-seedance-2.0Machine-readable model catalog: /docs/models.json. API definition: /docs/openapi.json.
Open the console to create an API key. Bank transfer and VAT invoice supported.
Text models use an SDK base URL swap. Visual models use /v1/video/generations to submit async tasks.
Text calls return in real time; visual tasks are polled until completion. Usage records can be exported for reconciliation.
/v1/modelsQuery current callable model IDs before integration.
/v1/chat/completionsOpenAI-compatible endpoint for SDKs, agents, and tools.
/v1/messagesAnthropic Messages-compatible endpoint for Claude clients and SDKs.
/v1/video/generationsSubmit a visual generation task and receive a job ID and polling URL.
/v1/video/generations/{task_id}Poll task status, failure reason, and download URLs.
Advanced text capabilities and visual model async task examples — cURL / Python / JavaScript shown for each scenario.
request_id, OpenAI id and system_fingerprint), identical to a direct upstream call. Visit the transparency page to inspect the database schema and confirm we do not store prompt or response bodies.
"stream": true in the request. Visual models are not streaming responses; submit a task, then poll /v1/video/generations/{task_id} for the result.
POST /v1/video/generations. The response returns job_id and poll_url. After completion, the polling response or "Visual model usage detail" shows the result, download URL, and failure reason.