Blaxel APIs allow you to interact with all resources inside of and across your workspace(s).Documentation Index
Fetch the complete documentation index at: https://docs.blaxel.ai/llms.txt
Use this file to discover all available pages before exploring further.
Get started
Authentication to the Blaxel APIs can either be done using API keys created from the Blaxel console, or through a classic OAuth 2.0 flow. API keys allow you to get started quickly. Simply generate an API key for your user or service account and use the API key as a bearer token in place of the authorization headersAuthorization or X-Blaxel-Authorization in any call to the Blaxel APIs.
For example, to list models:
Inference API
Run inference requests on your deployments.
Billing API
Programmatically retrieve cost and usage metrics.
Management API
Manage agents, functions, policies and much more.
API Versioning
The Blaxel API uses header-based versioning to evolve response formats and behavior without breaking existing clients.Version Header
All requests should include theBlaxel-Version header:
Version Format
Versions follow a Stripe-style date-based format:- Stable:
YYYY-MM-DD(e.g.,2026-04-16) - Preview:
YYYY-MM-DD.preview(e.g.,2026-04-16.preview)
Default Behavior
If you omit the
Blaxel-Version header, the API defaults to the earliest stable version (2026-04-16). This ensures backward compatibility — existing clients work without changes.Pinning to a Specific Version
To guarantee consistent response shapes across API updates, pin your client to a specific version:Unknown Versions
If you send an unsupported version, the API returns400 Bad Request:
Version History
| Version | Released | Status | Notes |
|---|---|---|---|
2026-04-16 | 2026-04-16 | Stable | Initial version |
