Supported Interfaces
ZBStream currently offers model listing, the OpenAI-compatible chat API, the Anthropic-compatible Messages API, plus multimodal and embedding endpoints. Query the model list first; actual capability follows the configured channels.
Public Routes
| Method | Path | Purpose |
|---|---|---|
| GET | /v1/models | List models available to the API key |
| POST | /v1/chat/completions | OpenAI-style chat completions |
| POST | /v1/messages | Anthropic-style Messages requests |
Unified Authentication
Public endpoints authenticate with a Bearer API key (the Anthropic routes also accept x-api-key). Model listing requires a valid key as well but consumes no credits. Never expose the full key in browser front-ends, logs, or screenshots.
Authorization: Bearer $ZBSTREAM_API_KEY
Content-Type: application/jsonPre-Integration Checklist
- Fetch available model ids from GET /v1/models instead of hard-coding them.
- Identical paths do not imply identical fields or response formats across channels.
- Messages and Chat Completions have different request structures — build the body for the route you chose.
Note
A route being available does not mean a specific model supports vision, tool calls, structured output, or reasoning — those follow the current model and channel configuration.