OpenAI API Pricing — KeyoAPI GPT-Class Rates vs Typical List
This page compares indicative KeyoAPI sell rates for current GPT-class IDs with typical public OpenAI list bands (GPT-5.4 / mini), then shows how to call them on one OpenAI-compatible base URL and prepaid wallet.
Price comparison table
| Model ID | Typical official / context | KeyoAPI | Notes |
|---|---|---|---|
deepseek-v4.1-flash |
OpenAI GPT-5.4 mini list ~$0.75 / $4.50 per 1M in/out (confirm on openai.com/api/pricing) | ~$0.45 / $1.80 per 1M in/out | High-volume / batch · /pricing/deepseek-v4.1-flash |
gpt-6-astra |
OpenAI GPT-5.4 list ~$2.50 / $15.00 per 1M in/out (confirm on openai.com/api/pricing) | ~$1.84 / $9.19 per 1M in/out | Flagship GPT-class · /pricing/gpt-6-astra |
gpt-5.6-luna |
OpenAI GPT-5.4 mini list ~$0.75 / $4.50 per 1M in/out (confirm on openai.com/api/pricing) | ~$0.10 / $0.62 per 1M in/out | Cheapest GPT-class twin · /pricing/gpt-5.6-luna · /model/gpt-5.6-luna |
Prototype free, then promote to GPT-class
For $0 prototyping on the same API key, use free catalog IDs on /free-models (fair-use limits). When quality gates pass, switch model= to gpt-6-astra, gpt-5.6-luna, or deepseek-v4.1-flash without changing base URL or auth.
Rates and how to call
Teams that search OpenAI API pricing usually need GPT-class chat inside an OpenAI SDK with clearer unit economics — or one prepaid balance that also covers Claude, DeepSeek, Whisper, OCR, and TTS. Official OpenAI surfaces win on brand trust and first-party features. KeyoAPI is for when you want that stack without five invoices and without rewriting clients when you swap models.
Keyo rates in the table are indicative sell prices from the live Keyo catalog. Always confirm interactive pages under /pricing/gpt-5.6-luna, /pricing/gpt-5.6-terra, and /pricing/gpt-5.6-sol before contracting volume. OpenAI list bands, cached-input discounts, and model renames change — treat official figures as planning context only. Keyo GPT-5.6 IDs are GPT-class twins on an OpenAI-compatible API, not a claim that they are OpenAI first-party model names.
Worked planning example (indicative only): suppose a batch path burns 50M input tokens and 10M output tokens per month. At Luna ~$0.10 / $0.62 per 1M in/out that is roughly $5 input + $6.20 output ≈ $11.20 before retries and overhead. At Terra ~$0.37 / $2.21 the same mix is roughly $18.50 + $22.10 ≈ $40.60. Put high-volume classification on Luna and keep product chat on Terra so the expensive model only sees the traffic that needs it. Re-run the math on live /pricing pages before you budget.
Integration steps: (1) create an account at /sign-up and top up Wallet; (2) create an API key in console; (3) set base URL https://www.keyoapi.xyz/v1 (OPENAI_BASE_URL or sdk base_url); (4) call POST /v1/chat/completions with model gpt-5.6-luna, gpt-5.6-terra, or gpt-5.6-sol; (5) try/buy interactively from /pricing/{modelId} — there is no separate upload playground. Longer guides: /model/gpt-5.6-luna, /model/gpt-5.6-terra, /model/gpt-5.6-sol.
Routing tip: keep GPT-class for product chat defaults; shift bulk classification, tagging, and draft rewrites to gpt-5.6-luna or deepseek-v4-flash on the same key. Escalate only failing slices to Terra or Sol after automated validators reject output. For Claude dollars see /claude-api-pricing; for Gemini see /gemini-api-pricing; for DeepSeek see /deepseek-api-pricing; for free prototyping see /free-models; for a side-by-side catalog see /compare.
Cost hygiene that actually moves the bill: truncate unused chat history, prefer structured short outputs for batch jobs, cache identical prompts by hash, and measure tokens from the response usage object rather than guessing. Confirm live Keyo sell rates on Model Square after every catalog change.
# cURL — GPT-5.6 Luna chat
curl https://www.keyoapi.xyz/v1/chat/completions \
-H "Authorization: Bearer $KEYO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gpt-5.6-luna","messages":[{"role":"user","content":"Classify this ticket: refund for order 42"}]}'
# Python — OpenAI SDK pointed at Keyo
from openai import OpenAI
client = OpenAI(base_url="https://www.keyoapi.xyz/v1", api_key="YOUR_KEYO_API_KEY")
r = client.chat.completions.create(
model="gpt-5.6-terra",
messages=[{"role": "user", "content": "Summarize this log line in one sentence."}],
)
print(r.choices[0].message.content)
FAQ
Is Keyo cheaper than OpenAI API pricing?
Often on the Keyo rows we list versus current OpenAI GPT-5.4 / mini list bands — but OpenAI’s public list, prompt caching, and batch discounts change. Treat this table as a planning snapshot and verify both sides before you commit.
Are gpt-5.6-* the same as OpenAI GPT-5?
No. They are Keyo GPT-class model IDs on an OpenAI-compatible gateway. Use them when you want OpenAI SDK shape and Keyo unit economics; confirm live rates on /pricing/{id}.
Do you offer a free OpenAI / GPT model?
Not as an OpenAI-branded free ID. Use Keyo’s permanent $0 DeepSeek/GLM/Kimi free twins to prototype on the same key, then promote to paid GPT-5.6 IDs when you need that quality band.
How do I try GPT-class models on Keyo?
Create a key at /sign-up, then open /pricing/gpt-5.6-terra (or Luna/Sol) for interactive try/buy. There is no separate upload playground — Model Square is the try path.
How do I estimate monthly GPT-class cost on Keyo?
Multiply expected input/output millions of tokens by the live /pricing/gpt-5.6-luna (or Terra/Sol) rates. Add retry overhead. Use /compare when you want a side-by-side planning table.
Can I keep my OpenAI Python/Node SDK?
Yes. Change base_url to https://www.keyoapi.xyz/v1 and the API key to your Keyo key, then pass a Keyo model id such as gpt-5.6-terra.