Each model has its own cost curve.
Flagship reasoning models, efficient chat models, image generation models, and video models can use different units and provider economics.
Pricing guide
Understand how AllToken pricing is shaped by model choice, provider route, and usage unit, while keeping billing and cost visibility in one account.
How pricing works
A simple text request, a multimodal request, and an async video task do not share the same cost structure. The practical way to evaluate spend is by model, route, and unit.
Flagship reasoning models, efficient chat models, image generation models, and video models can use different units and provider economics.
A model may be available through more than one route. AllToken keeps route selection and billing in one integration surface.
Text is commonly token-based. Image and video workflows may use generated outputs, async task state, duration, or resolution.
Categories
The public guide explains cost structure without pretending every live model price belongs on one static page.
Chat, reasoning, embeddings, and text generation are usually understood through input and output token usage.
Vision requests may include image input. Image generation is usually evaluated by generated output and task settings.
Video pricing depends on model, mode, duration, aspect ratio, resolution, and final task settlement rules.
Cost visibility
Pricing varies by model, route, and usage. The useful comparison is how many systems, invoices, and route decisions your team has to manage.
Video pricing note
Seedance access through AllToken should be evaluated on availability, API usability, and competitive pricing visibility. Region availability and current details may vary by model and backend supply.
FAQ
Sensitive billing policy should be confirmed in the model page, console, docs, or billing decision notes before launch.
Check the current console and account plan details. This public page does not invent promotional or free-tier policy.
AllToken is designed to reduce provider-by-provider setup by giving teams one API and billing layer for supported routes.
Failed request treatment depends on backend settlement rules and task state. Confirm the current policy in billing documentation before production use.
Video generation is async and may depend on model, duration, aspect ratio, resolution, generated output, and final settlement.
Image generation can follow task and generated-output semantics. Use current docs or console details as the source of truth.
Use model details, request patterns, and test traffic to estimate before scaling production usage.
Use the model catalog, model detail pages, or authenticated console where available.
Live prices, discounts, and provider routes can change. Use model pages and account usage records as the source of truth.
Start
Browse models, read the docs, then route production traffic through the AllToken account and billing surface when you are ready.