No SDK rewrite required
Continue using the official OpenAI Python client and its familiar chat-completions method.
OpenAI-Compatible API
VoyageAge is an OpenAI-compatible API provider for developers who want to keep their existing OpenAI SDK workflow. Change the endpoint to access supported OpenAI and Claude models through one multi-model AI API, with pay-as-you-go billing and lower-cost API access.
from openai import OpenAI
client = OpenAI(
api_key="YOUR_VOYAGEAGE_API_KEY",
base_url="https://api.voyageage.com/v1",
)
response = client.chat.completions.create(
model="gpt-5.6-sol",
messages=[
{"role": "user", "content": "Hello"}
],
)Change the connection, not the client
If your application already uses a standard OpenAI client, connect it to VoyageAge by updating the API key and base URL. Choose a model identifier from /v1/models when your current name does not match the VoyageAge catalog.
Continue using the official OpenAI Python client and its familiar chat-completions method.
Keep the standard messages structure while selecting a supported model through one gateway.
Use streaming and tool or function calls on compatible models and endpoints; validate model-specific behavior before production.
A unified AI API workflow
Use one API key, one billing system, and one compatible request format across the supported model families in the shared VoyageAge catalog.
GET /v1/modelsHTTPSgpt-5.6-solgpt-5.6-terragpt-5.6-lunaclaude-opus-5claude-fable-5claude-opus-4-8The displayed model list is derived from the same build-time pricing snapshot used elsewhere on VoyageAge. Current availability can depend on your API key and the live /v1/models response.
Compatibility as infrastructure
An OpenAI-compatible LLM API lets teams preserve a familiar integration boundary while changing where supported requests are served.
Keep a familiar OpenAI client and request shape instead of maintaining a separate SDK integration for every model provider.
Select another supported model ID while keeping authentication, billing, and the surrounding API workflow in one place.
Connect tools and agents that support a custom OpenAI-compatible endpoint. Always validate the specific client and model you plan to use.
Use one API key, one usage view, one wallet, and one compatible request format across supported model families.
Shared model pricing
Compare VoyageAge input and output prices with the official reference prices in the shared model-pricing source. Prices are shown per one million tokens.
Understand the distinction
OpenAI-compatible describes the request workflow; it does not mean a provider is the official OpenAI service. VoyageAge is an independent third-party API provider and gateway.
Use the official OpenAI API when you specifically need a direct OpenAI-operated service. Use VoyageAge when a compatible multi-model gateway better fits your application.
Practical workloads
VoyageAge fits server-side and tool-based workflows that benefit from a compatible endpoint and access to more than one model family.
Backend services, SaaS products, and customer-facing AI features that call model APIs.
Coding tools that accept a custom OpenAI-compatible endpoint and supported model ID.
Agents, workflows, and scheduled processes built around API requests.
Teams managing integration complexity and model spend as products evolve.
Applications that need access to both GPT and Claude model families.
A controlled provider change
Move from the official OpenAI API or another compatible provider by changing connection settings first, then testing your actual model and feature requirements.
client = OpenAI(api_key="OPENAI_API_KEY")client = OpenAI( api_key="YOUR_VOYAGEAGE_API_KEY", base_url="https://api.voyageage.com/v1" )Implementation questions
Clear answers about SDK compatibility, Claude access, migration, streaming, tool calls, and billing.
An OpenAI-compatible API follows familiar OpenAI request conventions so existing clients can usually connect through a custom base URL and API key. Compatibility does not mean the service is operated by OpenAI, and model-specific behavior can still vary.
Yes. VoyageAge provides an OpenAI-compatible endpoint at https://api.voyageage.com/v1 for supported models and workflows. VoyageAge is an independent third-party API provider, not an OpenAI service.
Yes. Configure the OpenAI client with your VoyageAge API key and the VoyageAge base URL, then choose a supported model ID returned by /v1/models.
Yes. VoyageAge exposes supported Claude models through its unified model catalog. It also provides an Anthropic-compatible gateway for clients that require Anthropic-specific behavior.
Usually not. Most integrations can keep the OpenAI SDK and request format while changing the API key, base URL, and model identifier when required. Test the exact features your application depends on before switching production traffic.
VoyageAge supports streaming responses and tool or function calls on compatible models and endpoints. Support can vary by model, so validate the selected model and client workflow.
The official OpenAI API is operated by OpenAI and serves OpenAI models. VoyageAge is an independent third-party gateway that uses an OpenAI-compatible workflow to provide supported OpenAI and Claude models through one account and billing system.
Yes. Add balance to your wallet and pay for the API usage you consume. A recurring subscription is not required to start using the API.
Start with one test request
Create an account, generate an API key, update your endpoint, and start testing multiple AI models through one OpenAI-compatible API.