APIPricingBillingDevelopers
API Pricing
API capabilities, billing units, budget controls, and developer pricing model.
API Billing Positioning
API pricing is documented separately from general subscription pricing, but it should reuse organization subscriptions, credit balance, model cost, and task usage. This first version provides the pricing framework; final API unit prices, packages, concurrency limits, and SLA rules will be added after the developer API spec is confirmed.
Billable Units
- Model calls: image, video, comic asset, and AI tool tasks consume credits or API quota.
- Input resources: reference images, videos, audio, and large assets may affect processing cost.
- Output specs: resolution, duration, count, batch size, and retry strategy affect final usage.
- Concurrency and priority: high concurrency, priority queue, and enterprise SLA can become developer plan capabilities.
API Plan Shapes
API In Subscription
Pro or higher tiers can reserve API access for connecting Lumeart to internal workflows.
Usage-Based
For developers with variable usage, billed by task type and model capability through credits or API quota.
Enterprise Contract
For high concurrency, custom models, independent SLA, dedicated support, and invoice billing.
Budgets And Risk Controls
- 1API key managementDevelopers should separate test and production keys, with rotation and disable controls.
- 2Budget controlOrganizations and projects need credit, rate, concurrency, and retry limits.
- 3Usage auditEach API call should preserve request_id, task_id, model, usage, status, and error reason.