Usage and Billing
RouteAPI records billing information based on request usage, account balance, and available discounts.
Text billing
Section titled “Text billing”Usually includes:
| Field | Description |
|---|---|
| prompt tokens | Input tokens |
| completion tokens | Output tokens |
| total tokens | Total input and output tokens |
| cached tokens | Tokens that hit cache, if included in this response |
| discount | If the account has a discount, it is reflected in the final billed amount |
Multimodal and task billing
Section titled “Multimodal and task billing”Image, audio, video, asynchronous task, and similar requests may not be billed only by tokens. They may also be billed by:
- Number of images
- Image size
- Audio duration
- Video duration
- Number of tasks
- Actual processed amount
Are failed requests billed?
Section titled “Are failed requests billed?”It depends on where the failure occurs:
| Scenario | Possible billing |
|---|---|
| Invalid Token | Usually not billed |
| Insufficient user balance | Usually not billed |
| Request not processed by the platform | Usually not billed |
| Request processed but returned an error | May be billed |
| Streaming output interrupted midway | May be billed by generated content |
Recommended usage log fields
Section titled “Recommended usage log fields”- Request time
- User and Token
- prompt tokens
- completion tokens
- Billed amount
- Discount information
- Error information
- Request latency