Claude Standard
StartupAPI Standard traffic is routed through Kiro via PayGo.
This is our lower-cost routing path for supported Claude models.
FAQ
How StartupAPI works
Direct answers about the service, its models, and how customer funds are handled.
How does pricing work?
StartupAPI uses prepaid credits. A request places a temporary reservation against the available balance, then settles uncached input, cache-write, cache-read, and output usage with the production weights. Unused reservation is released.
Are the models real?
Each request uses the identifier you send from StartupAPI's enabled customer catalog. StartupAPI does not silently switch to a different provider family. Identifiers in examples can change, so verify them on the live Models/Pricing page.
Stability
Provider availability can vary. A failure before billable usage releases its reservation without a usage charge. A partial delivered stream is settled for delivered usage, even when it ends with a disconnect, timeout, or limit event. An ambiguous no-usage stream can enter settlement review.
Reservations and payment reviews
Unused request reservations are releases of held credits, not separate promotional refunds. For a payment dispute, pending settlement, or account-credit question, contact StartupAPI support with the request or payment ID and never include your API key.
Upstream 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.