Quick Start
Start with your first request, choose the OpenAI, Anthropic Messages, or Responses API protocol, and learn when to switch to async task mode.
Choose a Compatible Protocol
https://nexusflow.hk/v1/chat/completionshttps://nexusflow.hk/v1/messageshttps://nexusflow.hk/v1/responsesPrerequisites
- Signed up and signed in to the nexusflow platform
- Created at least one API Key on the API Keys page
- Added balance on the Billing page
Install the SDK
Uses the OpenAI SDK by default. If you already have an Anthropic client or need the Responses API, see the corresponding protocol docs.
Configure the API
Point base_url to nexusflow and use a single API Key to access all models.
Make a Chat Request
Use the sync endpoint for text and reasoning models. The example below uses Qwen3.5 Plus.
Integrate Async Tasks
When you start integrating image or video generation, we recommend using /v1/tasks. This pipeline is better suited for high-latency models, background batch jobs, and high-concurrency queuing.
High-Concurrency Integration Tips
- Switch models by replacing the
modelparameter with another model ID - All models share a single API Key — no separate applications needed
- The OpenAI, Anthropic Messages, and Responses API protocols share the same balance and usage records
- Streaming is supported — just set
stream: true - Use
/v1/tasksfor image and video to avoid synchronous blocking
For repeated system prompts or long document context, enable enable_context_caching: true (OpenAI protocol) or the cache_control annotation (Anthropic protocol). Cache hits are billed at only 10% of the input price. See billing details.