Multi-model routing
Route requests across enabled models with configured priorities and model IDs.
OpenAI-compatible API for routing text, vision, and video models. Configure model and provider priorities once, then keep billing and cost visibility in one place.
Keep your OpenAI SDK pattern, replace the base URL, and start routing across text, vision, and video models through AllToken.
Generate one AllToken key for your app, environment, or team workflow.
Point your existing OpenAI-compatible client to the AllToken endpoint.
Choose a model or set routing priorities for cost visibility, provider availability, and capability.
const client = new OpenAI({
apiKey: process.env.ALLTOKEN_API_KEY,
baseURL: "https://api.alltoken.ai/v1"
});AllToken focuses on the operating work around model access: routing policy, provider setup, billing, and visibility.
Route requests across enabled models with configured priorities and model IDs.
Keep familiar SDK patterns and switch providers by changing endpoint and model fields.
Define provider priorities and fallback paths for provider issues without promising zero downtime.
Use one account balance and one billing layer across supported providers.
Compare effective tradeoffs before choosing a route policy for production traffic.
Reach more than text models through the same API surface as capabilities expand.
AllToken gives developers a single integration point for model categories that usually require separate provider accounts and setup paths.
Use leading text models for chat, coding, analysis, and agent workflows.
Route to models that can inspect images and support multimodal product experiences.
GPT Image 2 (and more soon) through the same API surface.
Add video generation workflows without building a separate provider integration.
Seedance 2.0 is highlighted as a video model available through AllToken, with conservative messaging around region availability and competitive pricing.
AllToken focuses on operational value before spend optimization: fewer provider accounts, clearer billing, and better cost visibility in one place.
Yes. AllToken is designed around familiar OpenAI-compatible request patterns so most clients only need a base URL and API key change.
AllToken lists supported text, vision, and video models in the model catalog, including provider and pricing details where available.
You can choose model IDs directly or configure priorities that help decide which enabled route should handle a request.
Pricing depends on the model, provider path, and usage. AllToken helps compare effective costs without relying on unverified lowest-price claims.
Seedance 2.0 and other multimodal capabilities are positioned as part of the AllToken API surface where available.
AllToken can expose configured fallback paths and provider priorities; exact behavior should match the backend routing policy.
Create a key, point your client to AllToken, and compare model paths without wiring every provider by hand.