Direct
One relationship per provider.
- 4 accounts
- 4 agreements
- 4 invoices
AI API infrastructure
Run Anthropic, OpenAI and xAI models through one OpenAI-compatible API. One key, one prepaid balance, per-request cost visibility, and lower pricing on eligible models. Eligibility is decided per model. Where there is a verified advantage, the direct price and the Astrodyne price are shown side by side before you send traffic.
For AI products and agents where one action triggers many model calls. Sign up, add funds and generate a key yourself — no sales call. Sending requests is invite-only while we roll out.
Agent economics
A multi-step agent turns one customer action into a long tail of model calls — planning, retrieval, reasoning, tool use, retries and verification each add inference cost. Every one of those calls gets its own request ID, tokens and charge, and they all settle against one prepaid balance.
Astrodyne is the model API underneath your agent, not the agent. Planning, retrieval, tool use and orchestration stay in your application.
Astrodyne for agents →Model ecosystem
One integration reaches every family below, and Astrodyne runs the model
you name — never a substitute. Your console and
GET /v1/models show the live models
available to your account.
Families are listed from the launch catalogue. Astrodyne runs the model you name and does not substitute a different one.
Why Astrodyne
As your product makes more model calls, model economics become infrastructure. A small per-token difference is negligible on one request and meaningful across millions.
Large AI buyers can get better commercial terms by consolidating demand and holding direct provider relationships. Astrodyne aggregates that infrastructure behind one API, so smaller accounts can reach those economics without negotiating separately with every provider.
One relationship per provider.
One relationship, the same reach.
You keep the account, the key and the balance. Astrodyne keeps the provider relationships.
Cost
Eligibility is decided per model, not across the catalogue. Where Astrodyne has a verified advantage we publish both figures side by side, so you can check the arithmetic rather than take a percentage on trust.
Pick a model
Verified model comparisons appear here as prices are approved — a figure is published only when there is an approved Astrodyne price and a current published direct price to compare it against. How we compare prices.
Integration
Keep the stack you already have. Anything speaking the OpenAI API — your client, or the model layer beneath your agent — reaches Astrodyne by changing the base URL and key.
base_url="https://api.openai.com/v1"
base_url="https://staging.astrodyne.ai/v1"
api_key=OPENAI_API_KEY
api_key=ASTRODYNE_API_KEY
Two lines. The OpenAI SDK works unchanged.
import os
from openai import OpenAI
client = OpenAI(
base_url="https://staging.astrodyne.ai/v1",
api_key=os.environ["ASTRODYNE_API_KEY"],
)
resp = client.chat.completions.create(
model="YOUR_MODEL_ID",
messages=[{"role": "user", "content": "Hello"}],
)
print(resp.choices[0].message.content)
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://staging.astrodyne.ai/v1",
apiKey: process.env.ASTRODYNE_API_KEY,
});
const resp = await client.chat.completions.create({
model: "YOUR_MODEL_ID",
messages: [{ role: "user", content: "Hello" }],
});
console.log(resp.choices[0].message.content);
curl https://staging.astrodyne.ai/v1/chat/completions \
-H "Authorization: Bearer $ASTRODYNE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "YOUR_MODEL_ID",
"messages": [{"role": "user", "content": "Hello"}]
}'
YOUR_MODEL_ID is a placeholder — replace it with a model ID from your console. See the compatibility guide for supported fields and known differences.
Risk
Astrodyne sits in your request path. These are properties of the implementation, not promises about it.
How security works · How we compare prices · Compatibility scope
How it works
Point your OpenAI-compatible client at the Astrodyne base URL with an Astrodyne key.
Send the model ID you want. Your account sees exactly the models it can call.
Every request returns an ID. Look it up for the model, status, tokens, latency and charge.
In the console
Look up any request by ID and see its model, status, tokens, latency and charge, against one balance — no estimating backwards from a monthly invoice.
Capabilities
One OpenAI-compatible API instead of a client, an auth scheme and a billing relationship per vendor.
Look up a request by ID and see its model, status, tokens, latency and charge.
Where Astrodyne has a verified advantage, the direct rate and the Astrodyne rate are shown side by side, per model.
One prepaid balance in US dollars. Settled usage is charged at the approved price for the model you used.
Useful for AI agents, apps, automations, prototypes and production workflows.
Cost mechanics
Every product with real usage pays this arithmetic once per call. An agent pays it many times over for a single user action.
A chat turn is one call. An agent that plans, retrieves, uses a tool, checks itself and retries is a dozen — from the same click.
Priced separately, per million tokens, and output is usually the dearer side — a short prompt with a long answer can cost more than the reverse.
System prompts and retrieved context are re-sent on every call, so a prompt you wrote once is a cost you pay on every request.
Identical token counts cost different amounts on different models — across one family the range can exceed ten times.
A fraction of a cent per call is invisible in testing and is the whole bill at volume.
So the per-call number is the one to watch — it is the figure that multiplies. Astrodyne prices per model and shows what each call cost.
The catalog
Every model on the launch plan. Each becomes callable when its price is approved — the catalogue in your console is always the list your key can actually reach.
On the launch plan, not yet callable. They appear in your console once they are.
Sending requests is invite-only while we roll out. Astrodyne runs the model you name — it does not choose a different one for you.
FAQ
One OpenAI-compatible API for leading models, with keys, a Playground, a per-account model catalogue, a prepaid balance and per-request cost.
Yes. Point an OpenAI-compatible client at the Astrodyne base URL with your key. The compatibility guide lists supported fields and known differences.
Yes — it is the case the pricing and visibility are sharpest for. Your agent runs in your application; Astrodyne is the model API it calls, and every call gets its own request ID, tokens and charge.
No. Astrodyne does not plan, retrieve, call tools, hold memory or orchestrate anything — it is the model API underneath whatever does. If your framework speaks the OpenAI API, point it at Astrodyne and keep it.
The ones available to your account, listed in your console and at GET /v1/models. What you see there is what your key can call.
No. You name the model and Astrodyne runs that model. It never substitutes a different one.
Yes, over server-sent events, through the same Chat Completions endpoint.
Yes. The Playground sends real requests through the same path your code uses, with a key held in memory only.
Astrodyne aggregates demand and maintains the provider relationships behind one API. That lets eligible accounts access commercial terms normally associated with larger buyers, without negotiating each provider relationship themselves. Availability and pricing advantages vary by model.
Only where Astrodyne can show it. A price comparison is published for a model when there is both an approved Astrodyne price and a current published direct rate to compare against; where that is not available, the pricing page says so rather than implying a saving.
Every call carries its own charge, so you can see which steps of an agent run are expensive rather than inferring it from a monthly total. Spend cannot exceed the balance you funded, so a runaway loop stops at the limit. And where a model has an approved Astrodyne price below the vendor's published direct rate, both figures are shown side by side.
(input tokens ÷ 1,000,000 × input rate) + (output tokens ÷ 1,000,000 × output rate), multiplied by the number of requests. The LLM cost calculator does this for you.
Send fewer input tokens by trimming system prompts and retrieved context, cap output length where the task allows, and use a smaller model for work that does not need a larger one. Per-request cost visibility shows which calls actually dominate the bill.
The same levers apply: less input context, capped output, and the smallest model that does the job. Because input and output are priced separately, a long answer can cost more than a long prompt.
Yes. Enter your typical input and output token counts and expected request volume in the calculator. Where a verified price and a published direct rate both exist for a model, the two are shown side by side.
A single API in front of multiple model providers, handling authentication, request routing, billing and usage visibility so you do not integrate each provider separately.
The same idea, usually said of text models specifically. The terms are used interchangeably and there is no formal distinction.
That is the purpose of the gateway: one OpenAI-compatible surface across model families. Which specific models your key can call is account-specific and listed in your console and at GET /v1/models.
Both are hosted gateways offering many models through one API. Compare them on deployment, billing model, whether model selection is explicit or automatic, and whether you can see the cost of an individual request. We do not publish claims about another product's current behaviour.
The structural difference is deployment and billing: Astrodyne is hosted and holds one prepaid balance, where a self-hosted proxy is run by you against your own provider accounts and invoices.
You top up a prepaid balance in US dollars and are charged for settled usage at the price shown for that model. Every request's charge is visible on its own.
Eligible models are priced below the vendor's published direct rate. Eligibility is per model, and we publish a comparison only when there is an approved price and a current published rate to compare against.
No. Customer-facing surfaces show a neutral catalogue and sanitized request data.
Developers, small teams and agencies who want one integration and one bill instead of one of each per vendor.
You can create an account and explore the console. Sending requests is invite-only while we roll out.
Your next step
Build your AI product or agent against one OpenAI-compatible API, choose the models each workload needs, and see the cost of every request. Sending requests is invite-only while we roll out.