Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.quiver.ai/llms.txt

Use this file to discover all available pages before exploring further.

The API uses prepaid pricing credits. Your organization balance is stored in those integer credit units. The runtime subtracts pricing_credits amounts on each successful call—there is no fixed rule like “one generated SVG equals one unit off the balance.”

​
How usage maps to credits

Debits are per model and per operation. A single successful output can cost many credits (for example 30 per generation for some models), not one. Each model returned by GET /v1/models includes pricing_credits:
  • svg_generate — credits debited per generated SVG for that model (used by POST /v1/svgs/generations).
  • svg_vectorize — credits debited per vectorization for that model (used by POST /v1/svgs/vectorizations).
Examples (current defaults; always read the live model object for your integration):
  • One model might charge 30 credits per generation and 30 per vectorization.
  • Another might charge 20 per generation and 15 per vectorization.
For generations, the n parameter means n outputs each cost svg_generate credits, so a successful request debits n × svg_generate credits in total (default n is 1). Vectorization requests debit svg_vectorize once per successful call. The legacy model.pricing USD strings are deprecated placeholders for older clients. Use pricing_credits for billing behavior.

​
Credits

Buy credits from the Billing page.
  • Per-credit price: default USD 0.01 per pricing credit (your organization may use a custom per-credit rate). That rate applies to every credit you buy; API usage then spends n × svg_generate or svg_vectorize credits per successful call, so dollar cost per output is roughly (credits debited) × (per-credit price)—for example about USD 0.30 per generation when svg_generate is 30 and the default USD 0.01/credit applies.
  • Purchase size: each checkout adds up to 60,000 pricing credits (the same units the API debits). The minimum is at least 600 credits and can be higher for your org so the charge meets the card processor’s minimum (typically USD 1) at your per-credit rate—the Billing page shows the effective min/max for your account.
  • Credits expire 1 year after purchase.
Monthly app subscriptions include weekly credits for the App product. Those subscription credits are not API balance and cannot be spent through api.quiver.ai. You can also enable automatic top-up in Billing to replenish credits when balance drops below your configured threshold.
Looking for monthly plans with included SVGs? Those are available in the App. See quiver.ai/pricing for details.

​
Custom pricing

For higher volumes or custom arrangements, contact sales. Per-organization overrides are stored as integer milicents per credit (1000 milicents = 1¢).