Billing & Limits
1. Billing and charging
You are billed on the usage the upstream reports in its response; nothing beyond the 4 MB request cap is billed extra. Charging happens after the response is delivered.
A failed charge never breaks a request that already succeeded: the response still returns 200, marked with the header X-Sub2Api-Charge: pending, and the recharge queue retries automatically.
2. Limits
- Request body is capped at 4 MB; larger bodies return 413.
- A user may hold at most 20 non-revoked keys.
- Only models that have a price registered here and an upstream account that declared the capability can be called.