Route with intent
Expose stable public aliases while Aethera selects enabled provider routes and keeps provider identity visible.
Explore models ↗
AETHERAROUTER v2.1
Aethera gives your team one OpenAI-compatible gateway for model routing, transparent usage, and budget-aware execution.
THE CONTROL SURFACE
Keep your application integration simple while Aethera handles the operational details.
Expose stable public aliases while Aethera selects enabled provider routes and keeps provider identity visible.
Explore models ↗Reserve against request budgets, settle from reported usage, and keep wallet movements in the ledger.
Open usage ledger ↗Test requests in the playground, inspect responses, then create an API key for your integration.
Start in playground ↗MODEL CATALOG
Select an active Aethera alias. Inspect provider, limits, pricing, and availability.
ACTIVE MODELS
Select a model
to inspect its route.
PUBLIC MODEL ALIAS
Aethera•OPERATIONAL
Live public model alias routed through an active provider route.
Loading live model catalog…
TRANSPARENT PRICING
Model rates are shown per one million tokens. Your request ledger records actual charges, while prepaid credits remain under your control.
Input and output rates are specific to each active model.
See live model prices ↗Balance is reserved for a request and settled from reported usage.
Review billing ledger ↗Eligible completed referred transactions earn the referrer USD.
Open referral page ↗Payment processing is not connected yet. Top-up requests require manual payment verification; credits are not added until confirmed.
THE REQUEST PATH
Use a workspace session or API key.
Keep your app connected to a stable public model ID.
Routing, reservation, provider call, and settlement stay observable.
Response and financial record arrive with the request trail.
FOR DEVELOPERS
Open the workspace, test a model in the playground, and move to an API key when your integration is ready.
Open developer portal →curl /v1/chat/completions -H "Authorization: Bearer ***" -d '{"model":"public-api","messages":[…]}'DOCUMENTATION / V2.1
Quickstart, endpoint reference, billing behavior, and error handling—all without leaving the landing page.
Open the workspace to test a model and create an API key. Keep the raw key private; it is shown only once.
curl https://api.aethera.com/v1/chat/completions \\
-H "Authorization: Bearer ${AETHERA_API_KEY}" \\
-H "Idempotency-Key: replace-with-unique-request-id" \\
-H "Content-Type: application/json" \\
-d '{"model":"public-api","messages":[{"role":"user","content":"Hello"}]}'Use a fresh idempotency key for each logical request. Repeating the same key and payload returns its stored result; reusing the key with a different payload returns HTTP 409. Keys are scoped to the authenticated user.
Send your API key as a Bearer token to public API endpoints. The authenticated workspace uses its browser session. Never place a key in client-side browser code.
Authorization: Bearer ${AETHERA_API_KEY}Never expose an API key in browser code or commit it to source control.
List enabled public aliases before making a request. Pricing and availability are controlled by the active server catalog.
Send a JSON body with a public model alias and messages. Include a unique Idempotency-Key header for each logical request; the endpoint rejects a missing key with HTTP 400.
/v1/chat/completions{
"model": "public-api",
"messages": [{"role": "user", "content": "Your prompt"}],
"temperature": 0.7
}Each completed request records usage and its wallet settlement in the request history and ledger. USD is the canonical billing currency.
Errors use JSON responses with a useful detail or normalized error message. Check the HTTP status and do not charge a failed request client-side. Request history and the ledger in the workspace are the source of truth.
When a request fails, inspect the response status and error payload before retrying. Use a new idempotency key only for a new logical request.