V1 Chat
POST /v1/chat/completions accepts bearer keys with chat scope and returns a familiar completion format.
The BLUN API is the technical layer for developers: chat, text, images, voice, agents and billing through clean endpoints.
API system
Developers start in the console, create keys, call the V1 API and then check usage in the same account.
POST /v1/chat/completions accepts bearer keys with chat scope and returns a familiar completion format.
/console/keys creates keys for chat, images, voice, agents and embeddings. Revocation takes effect immediately.
/console/usage reads /v1/usage for 7, 30, 90 days or the full period.
What API does for you
No demo windows, no empty promises. This page describes what the BLUN component actually does for users.
API keys are created in the account, scoped, and removed when you no longer need them.
Chat responses, longer jobs and status checks fit normal developer workflows.
Consumption, limits and cost stay traceable in the account.
Who it's for
BLUN is built for people who need to actually finish work: small businesses, teams, developers and operators.
Embed BLUN features directly into your own apps.
Connect client projects to a controllable AI layer.
Make models and tools usable across teams via fixed interfaces.
How it works
Open login or registration.
Set the scope and project.
Call the endpoint and see usage in your account.
Pricing
All four tiers are available through the central BLUN Account waitlist. There is no purchase or charge yet.
Frequently asked
No. You open BLUN in the browser. Developers also get API, CLI and MCP.
Yes. Starter, Pro, Pro Max, and Enterprise are on the waitlist. See /pricing for prices and status.
BLUN runs on its own infrastructure in Europe. Sensitive projects should not drift into foreign clouds uncontrolled.
Yes. You can join the waitlist for Starter, Pro, Pro Max, or Enterprise.
Test the component in your account or check pricing first. Clear flow, clear plans, clear next steps.