Vidbyte API pricing is usage-based, not route-package based
Pricing
Vidbyte API pricing is token based. The amount you spend depends on the input and output tokens used by a request, not on a flat per-route fee.
How it works
Token based
Each request is billed from token usage. Larger prompts, larger context payloads, and larger generated responses use more tokens than smaller requests, so cost scales with the actual work the model performs.
What to watch
Usage signals
Vidbyte returns token usage and pricing information in the response envelope so your application can observe what each request consumed. That makes it easier to reason about budgets, request size, and cost over time.
Response fields
Usage fields
{
"token_stats": {
"input_tokens": 382,
"output_tokens": 221,
"total_tokens": 603
},
"pricing": {
"total_cost": 0.0124
}
}Where to pay
Add API balance
API usage draws from the API balance connected to your account. If you are preparing a production integration, keep enough API balance available in settings before sending sustained traffic.