Zorveus Documentation

Overview of multi-provider wire protocols and inference capabilities supported on api.zorveus.com.

Zorveus sits between your applications and AI model providers, natively supporting the Anthropic /v1/messages wire protocol, standard OpenAI /v1/chat/completions, Google Gemini, and specialized audio, embedding, and realtime endpoints.

Supported wire protocols and endpoints

Provider format	Endpoints	Example SDK usage
Anthropic Native	`POST /v1/messages` `POST /v1/messages/count_tokens`	Standard Anthropic SDK (`@anthropic-ai/sdk`, `anthropic-python`)
OpenAI Chat Format	`POST /v1/chat/completions` `POST /chat/completions`	Standard OpenAI SDK (`openai`), Vercel AI SDK, LangChain
OpenAI Responses API	`POST /v1/responses` `POST /responses`	OpenAI Responses API format
Google Gemini Native	`POST /v1beta/models/*` `POST /vertex_ai/live`	Google GenAI SDK and Vertex AI live stream
Embeddings and Rerank	`POST /v1/embeddings` `POST /v1/rerank`, `POST /v2/rerank`	Cohere, Voyage, Jina, OpenAI embeddings and rerankers
Audio and Speech	`POST /v1/audio/speech` `POST /v1/audio/transcriptions`	OpenAI Whisper, TTS, Gemini Audio
Realtime Voice / WebSockets	`POST /v1/realtime/calls` `POST /v1/realtime/client_secrets` `WS /v1/realtime`	OpenAI Realtime API, WebRTC, and WebSocket client sessions

Inference modalities

Chat Completions

Standard and reasoning completions across OpenAI, Anthropic, Gemini, and open models.

Streaming Completions

Server-Sent Events (SSE) token streaming.

Tool Calling & Function Calling

Structured schema execution and agentic tool invocation.

Responses API

OpenAI-compatible response items for supported provider routes.

Embeddings

Dense text embeddings for semantic search and retrieval (RAG).

Model Discovery

Inspect dynamically available models and routing policy status.

SDK configuration

Different SDK clients append different default path prefixes. Configure the exact base URL matching your SDK:

SDK Client	Base URL parameter	Notes
OpenAI Python / TypeScript	`https://api.zorveus.com/v1`	OpenAI clients automatically append `/chat/completions`.
Anthropic Python / TypeScript	`https://api.zorveus.com`	Anthropic clients automatically append `/v1/messages`. Do not add `/v1`.
Zorveus SDK (@zorveus/sdk)	Default preconfigured	Connects automatically to `https://api.zorveus.com`.
Direct HTTP / cURL	Full route path	Use `https://api.zorveus.com/v1/chat/completions` or `https://api.zorveus.com/v1/messages`.

Point the base URL to Zorveus in your client initialization:

Client SDK / Framework:

import anthropic

client = anthropic.Anthropic(
    base_url="https://api.zorveus.com",
    api_key="zrv_your_api_key",
)

response = client.messages.create(
    model="claude-3-7-sonnet-20250219",
    max_tokens=1024,
    messages=[
        {"role": "user", "content": "Explain quantum computing in one sentence."}
    ],
)
print(response.content[0].text)

How Zorveus handles requests under the hood

Authentication and metering: The gateway intercepts your request (x-api-key: zrv_... or Authorization: Bearer zrv_...), validates the API key, and verifies active balance and credit caps.
BYOK injection and system routing: If your organization configured custom provider credentials (e.g. Anthropic or OpenAI API keys), Zorveus securely injects them with automatic multi-key failover. Otherwise, requests route through Zorveus system credentials.
Usage settlement: The gateway calculates token consumption and cost, then settles the ledger event in real time upon completion.

Was this page helpful?

Edit this page on GitHub

Inference overview