Language models
Evaluate enabled chat or reasoning variants for assistants, extraction, classification, and content workflows.
Use TokenRa to discover enabled Doubao and related ByteDance model capabilities from one account. Because language, image, and video products use different request patterns, begin by identifying the exact capability and model ID in the live console.
“Doubao API” can refer to multiple model capabilities rather than one interchangeable endpoint. Text models may use chat-style requests, while image and video generation can require dedicated parameters, uploaded references, asynchronous tasks, and polling.
Evaluate enabled chat or reasoning variants for assistants, extraction, classification, and content workflows.
Check prompt, reference-image, size, count, and output controls supported by the active image channel.
Plan an asynchronous task lifecycle for text-to-video or image-to-video models such as enabled Seedance variants.
Choose the capability before choosing the model name. Each media type has different latency, validation, cost units, and output handling requirements.
Do not send media prompts to a chat endpoint based only on the family name. Inspect the model in the console, follow the request contract for that capability, and validate every user-controlled media parameter.
Record whether the enabled model is text, image, video, or another task type, plus its exact model ID and supported inputs.
Send chat requests to the applicable compatible endpoint; create and poll asynchronous tasks for media models when required.
Check task status, content policy, media rights, latency, failure handling, and billed units before production rollout.
# Text models may use the compatible chat endpoint.
# Image and video models can use capability-specific task endpoints.
# Copy the exact endpoint and model ID from the TokenRa console.
TokenRa is a gateway with account-specific channel configuration. A model family appearing on this information page does not guarantee that every version or capability is enabled for every account.
Confirm the exact model identifier, endpoint, supported parameters, billing unit, and current rate in the model directory or console. Treat those live values as authoritative.
Availability depends on the channels enabled for your account. Check the live directory and console for the current model identifier and access.
Create a TokenRa API key, confirm the enabled model identifier, and use the request format documented for that capability. Applicable text models use an OpenAI-compatible endpoint; media models may use asynchronous tasks.
Pricing can vary by model version and active channel. Review the current billing unit and rate in the live model directory or console before testing.
Yes. TokenRa keeps credentials and account-level usage in one place. Request fields and model behavior can still differ, so run regression evaluations before changing production traffic.
“Doubao”, “ByteDance”, “Seedance”, and related names may be trademarks of their respective rights holders. TokenRa is an independent API gateway and this page is not an official vendor page or endorsement.