API Reference
nexusflow access is organized into three compatible protocols plus one async task API. OpenAI Chat, Anthropic Messages, and Responses API requests all flow through the same model routing, billing, and monitoring pipeline.
Three-Protocol Compatibility
OpenAI Chat, Anthropic Messages, and Responses API share one set of keys, billing, and monitoring.
Streaming Responses
Chat endpoints support SSE streaming, ideal for real-time interaction and low-latency experiences.
Async Tasks
Image and video use a unified task API, ideal for high-latency and high-concurrency scenarios.
Pre-Launch Validation
Combined with rate limits, error codes, and the monitoring page to help you spot traffic risks before production.
Compatible Protocols
OpenAI Chat
/v1/chat/completionsRecommended default, compatible with the OpenAI SDK.
Anthropic Messages
/v1/messagesReuse the Anthropic SDK and Messages format.
Responses API
/v1/responsesBuilt-in web search and code interpreter, simplifying multi-turn context management.
Public Gateway Protocol Scope
AvailableOpenAI Chat / Anthropic Messages / Responses APIText, reasoning, vision, coding, and specialized models are called per supported_protocols.
AvailableOpenAI Embeddings / Image Generations / NexusFlow TasksEmbedding, image, and video models use the corresponding endpoints by capability.
This page lists only the public APIs you can currently call directly at https://nexusflow.hk.
Basics
Base URL
https://nexusflow.hkAuthentication
Authorization: Bearer sk-air-xxxRequest Format
Content-Type: application/jsonResponse Format
JSON / Server-Sent Events / Task StatusRecommended Integration
Chat
Use `/v1/chat/completions` by default, compatible with the OpenAI SDK.
Protocol
If you already have an Anthropic client or need the Responses API format, use the corresponding compatible endpoint.
Tasks
Image and video models prefer `/v1/tasks` and `/v1/tasks/:id`; images also support OpenAI-style `/v1/images/generations`.