AI Model Pricing and Billing
Plan token, image, video, audio, embedding, and automation workflow costs with published model prices, request reserves, and usage logs.
Last verified: 2026-06-05
Billing and balance
MetisRouter pricing is usage-based. Token models bill by input and output tokens, while image, video, audio, transcription, and embedding models use their published unit.
- Paid API requests require at least 5 USD in account balance.
- Each request reserves at least 5 USD before execution and releases unused reserve after final billing.
- Requests that fail before an upstream model successfully runs are not charged for model usage.
Model prices
Public model pricing is shown in the model catalog and model details, then applied by the backend billing configuration.
- Use exact model IDs and endpoint types to avoid unexpected routing behavior.
- Check image, video, audio, cache, and parameter-based pricing branches before production use.
- Higher-volume or prepaid customers can use the high-volume sales inquiry link for volume discount discussions.
Cost calculator
The pricing page explains billing rules; the interactive calculator lives on a dedicated page for token, image, video, audio, embedding, and automation estimates.
- Estimate one bounded request before multiplying by monthly workflow volume.
- Calibrate with charged USD, tokens, asset counts, and request id in Usage Logs after the first request.
- Keep request reserve and minimum balance rules in mind before production traffic.
FAQ
How does MetisRouter calculate pricing?
The prices shown in the model catalog are the prices users pay on MetisRouter. Token models are billed by input and output tokens; image, video, speech, transcription, and embedding models use the published unit shown on each model.
Is there a minimum balance required to call the API?
Paid API requests require at least 5 USD in account balance, and each request reserves at least 5 USD before execution. After completion, MetisRouter deducts the actual usage cost and releases the unused reserve.
How do I estimate workflow cost?
Estimate one bounded request, verify the charged amount in Usage Logs, then multiply by expected workflow volume. Use calculators for token, image, video, audio, embedding, and automation planning.