Pricing
Pay for what you use, or plan with monthly credits.
Choose the commercial approach that fits your stage. Final rates are confirmed per model and per agreement.
Developer
Individual developers prototyping and evaluating models.
Pricing to be confirmedPay only for the tokens or units each request consumes.- Model access subject to availability
- Usage visibility in the console
- Documentation and community resources
Team
Startups and product teams shipping AI features to customers.
Pricing to be confirmedUsage-based access with shared visibility across the team.- Everything in Developer
- Shared workspace and member roles
- Budget planning and alert thresholds
Enterprise
Organizations with volume, procurement, or governance requirements.
Contact SalesCommercial terms discussed against your expected volume.- Requirements review with the team
- Support arrangements by agreement
- Guided technical onboarding
Compare plans
| Feature | Developer | Team | Enterprise |
|---|---|---|---|
| Commercial approach | Usage-based or monthly credits | Usage-based or shared credits | By agreement |
| Model access | Subject to availability | Subject to availability | Reviewed against requirements |
| Usage visibility | Personal dashboard | Workspace dashboard | Reporting discussed during onboarding |
| Budget planning | Basic alerts | Workspace budgets and alerts | Planned with the team |
| Team requirements | Single user | Members and roles | Governance requirements reviewed |
| Support arrangements | Documentation | Standard support channels | Defined by agreement |
| Enterprise onboarding | — | — | Guided onboarding |
Cost estimator
Illustrative estimate — not a quotationEstimate monthly token costs from your own assumptions. Rates are editable sample values in USD per one million tokens.
- Input cost
- $40.00
- Output cost
- $45.00
requests × ((input tokens × input rate) + (output tokens × output rate)) ÷ 1,000,000
Illustrative estimate — not a quotation. Actual rates depend on model, billing unit, and commercial terms.
FAQ
Billing questions
How tokens, credits, and billing units work.
Tokens are the usage units models consume. Credits are a prepaid platform balance. Usage is drawn from credits according to model-specific rates, which are confirmed as part of your commercial terms.
Generating output is typically more compute-intensive than reading input, so many providers set a higher rate for output tokens. The estimator lets you set each rate separately to reflect this.
No. Image generation is often billed per image, speech per character or second, and transcription per minute of audio. Each model listing shows its billing unit where it is known.
Credit amounts, rollover, and expiry policies are subject to agreement. This demo does not define binding credit entitlements.
Enterprise pricing is discussed against your expected volume, model mix, support arrangements, and requirements. Contact the team to start that conversation.