Claude Standard
StartupAPI Standard traffic is routed through Kiro via PayGo.
This is our lower-cost routing path for supported Claude models.
Pricing & credits
Understand how billing works
Prepaid StartupAPI credits fund billable model usage; reservation and settlement behavior depends on whether usage was delivered.
Subscription allowance units
Subscription allowances use weighted units. Model choice affects how many units your tokens use. Creating a prompt cache also uses units; reusing cached prompts uses less. Your usage page shows tokens and deducted units separately.
Five-hour windows reset from subscription activation. Requests rejected before processing use no allowance; recorded processing on interrupted requests may still count. Monetary formulas below describe Usage Credits (PAYG).
How billing works
- Credits are prepaid — you're never billed by surprise.
- Uncached input, cache writes, cache reads, and output use separate production weights and rates.
- A failure before billable usage releases the temporary reservation without a usage charge.
- A successful response or partial delivered stream settles the usage delivered. An ambiguous no-usage stream can enter settlement review.
Current models and rates
The live Models/Pricing page is the source of truth for enabled identifiers, model-specific context and output limits, Standard and Max pricing, and cache-read/write rates.
Open live Models & PricingUpstream Routing
Claude Max
StartupAPI Max traffic uses our dedicated Max routing infrastructure.
The underlying upstream provider and routing implementation are not publicly disclosed.
Max is the dedicated routing path for its exclusive model.
Claude Standard and Claude Max use separate routing paths.
Add credits
Choose an amount and complete payment. StartupAPI credits appear in your balance after payment confirmation.
Add Credits
Check your balance
Available credits, credits in use, pending settlement, and debt review are shown in your dashboard.
Open Dashboard