Skip to main content
OmniaKey exposes three protocol surfaces on one API host:
Use the protocol your SDK or coding agent already speaks. The same OmniaKey API key works across the public Claude, GPT, and Gemini catalog.

​
Base URLs

The Anthropic SDK appends /v1/messages by itself. Use the bare host for Anthropic-native tools.

​
Endpoint matrix

​
Public capability boundary

The current public documentation covers text and coding-agent workflows only:
  • OpenAI-compatible Chat Completions and Responses
  • Anthropic Messages for Claude Code
  • Gemini Generate Content
  • model listing, authentication, streaming, quota, and usage visibility
Do not assume image generation, audio, embeddings, rerank, files, fine-tuning, or batches are supported unless they are added to this docs site and shown in the dashboard catalog.

​
Model policy

OmniaKey does not silently substitute, quantize, or distill models. The model id you request is the model routed upstream. If a model is unavailable, the request fails instead of being hidden behind another model.

​
Billing

Requests spend from your prepaid account balance. Usage is metered per token and visible in the Dashboard. API keys can also have per-key spending caps.

​
Next steps

Authentication

API keys, headers, and SDK auth conventions

OpenAI-compatible API

Chat Completions, Responses, and Models

Errors & Rate Limits

Status codes, quota errors, and troubleshooting