What Astrolabe Cloud owns
- Hosted OpenAI-compatible gateway at
https://api.astrolabe.run/v1 - Workspace API keys minted in the Cloud app
- Prepaid credit balance and usage ledger
- Managed routing stack templates
- Custom routing stacks with policy boundaries and objectives
- Per-request stack selection through
metadata.astrolabe.stack - Route traces, response headers, and model-call records
Request flow
- Your app sends a request with an Astrolabe Cloud API key.
- The gateway authenticates the key and checks workspace status.
- Astrolabe reserves prepaid balance before provider work starts.
- The gateway resolves a routing stack from request, key, workspace, or managed default settings.
- The stack chooses an allowed serving model and fallback behavior.
- OpenRouter executes the selected model call.
- Astrolabe finalizes usage, updates billing, stores traces, and returns routing headers.
Default virtual models
Use virtual models when you want Astrolabe to choose the concrete provider model:astrolabe/autoastrolabe/codingastrolabe/researchastrolabe/visionastrolabe/strict-jsonastrolabe/cheapastrolabe/safe
Quickstart
Create a workspace key, add credits, and make your first hosted request.
Routing stacks
Learn how managed and custom stacks control model selection.
Customize stacks
Set model boundaries, quality targets, cost modes, fallback, verification, and trace behavior.
Call a stack
Select a specific stack in
metadata.astrolabe.stack.Model roster
Review public virtual models and hosted model pricing roles.
API reference
Check gateway endpoints, auth, headers, and error shapes.

