Skip to main content
Limits vary by access type, plan, endpoint, and model availability.

Text generation (/v1/chat/completions)

Token usage availability

Token usage is counted as input tokens plus output tokens. For Pro accounts, token availability is calculated across the monthly billing period based on your usage relative to the percentage of the billing period that has elapsed. You can check current allowance in the dashboard. After the Pro allowance is reached, requests can continue from a topped-up balance and are billed from the live model pricing. Pro token availability remains subject to model availability, service capacity, fair-use calculations, and abuse-prevention controls. Note: Maximum input sizes also depend on your access tier and the specific model context window.

Image API (/v1/images/generations, /v1/images/edits)

Image requests require a valid LLM7 API token and are billed from available allowance or balance. Image model metadata controls supported sizes, reference-image limits, and availability. Successful image responses include usage.cost_usd when billed cost is available.

Video API (/v1/videos)

Video requests require a valid LLM7 API token and are billed asynchronously from available allowance or balance. On task creation, the full estimated cost is reserved as a hold. For route-priced video models, select the route that matches the submitted model and request type, then use the route-level public price:
Fall back to seconds * pricing.price only when the model does not expose pricing.route_prices_usd_per_second. The hold is consumed when the task completes successfully and released when upstream generation fails or task creation is not accepted.
Use the Models API to inspect live model tiers, pricing, context windows, and capability flags. Get a free token at dash.llm7.io or upgrade to Pro for higher caps.