Docs just grew up.
https://t.co/2DwUtkCgTc
Images and Videos are in the docs now: gpt-image-2 generate / edit / save, and grok-imagine-video-1.5 from create โ poll โ MP4.
Quickstart now runs the whole loop โ credit, key, request, result, cost. API reference has Responses and streaming. Prices in the docs point at pricing.usd.json on the global site.
Nine pages. Same base URL.
GPT-6 #Astra is live now on BeefAPI!
Same key. Same OpenAI-compatible client. About 70% less than running it through the usual checkout โ public USD price before you send, a receipt after.
People whoโve been running it keep landing on the same feeling: Less like switching models, more like tuning one that actually listens.
Use it now: https://t.co/C2mD2NAKjy
When the next model drops, the setup shouldnโt change.
Same key, same @OpenAI -compatible client, public USD prices before you send, a receipt after.
Weโll add Astra the same way, soon.
Trying @Beef_api
as an early https://t.co/mN0Q23wgwm prepaid API for a bunch of models Claude, GPT, Grok, and more, up to 19. Same key, no dashboard hopping.What I like so far: you see the price before the call leaves, then you get a readable receipt after. That alone makes billing less painful. How to join the early tester flow: follow their X, join the Discord, and send feedback.If theyโre giving $100 credit to early testers, Iโm in and happy to keep stress-testing routing, latency, and tool use.
@ainonly01 Really appreciate your recommendation! We're still early on, so not everything is polished yet.
Please keep the feedback and criticism coming โ let's make BeefAPI better together!
Usage rows now open.
Click a request and you get the bill for that call: input, cache read, cache write, output, per-call or tool use. Each line is usage ร price = amount. The last line is Total charged โ same number as Cost in the list.
If long-context pricing applied, the receipt says so in one sentence. If we couldnโt observe usage, it says the charge was estimated โ we donโt invent a unit price.
Thatโs the product. One request, one receipt you can read.
When the next model drops, the setup shouldnโt change.
Same key, same @OpenAI -compatible client, public USD prices before you send, a receipt after.
Weโll add Astra the same way, soon.
We got tired of paying for models we could not reconcile.
Too many keys. Too many dashboards. A bill that never quite matched the traffic.
So we shipped BeefAPI. https://t.co/VYoOAURpG7
If you already speak OpenAI, you should not have to learn a new SDK.
๐OpenAI-compatible tools: https://t.co/GsPpgISSGM
๐Claude Code and other Anthropic-style tools:
https://t.co/TCNC0sxs0A
Create a key, keep it on your server, send a call. Codex CLI is documented the same way.
The setup is supposed to feel slightly boring. That is the point.