BLUNAPI

The BLUN API brings text and code into your own applications through a single access point. King already runs on api.blun.ai, with one schema for responses and streams via REST and SSE.

Create an API key Read documentation

King is available. Images, speech and transcription will follow.

API · REQUESTIllustrative demo

POST /v1/chat/completions Authorization: Bearer blun_key_… { "messages": [ { "role": "user", "content": "Summarize this document." } ] }

Response200 · text/event-stream

One access. Clear rules.

From the first key to usage, everything stays in the same account.

POST /v1/chat/completionsBearer blun_key_…scope: chat200 OK

One login, clear keys

API keys are created in your account, carry a scope, and can be revoked immediately.

One login, clear keys

The V1 API accepts bearer keys with chat scope and responds in a familiar completion format.

Create keys in your account, assign a scope, and delete them when needed
Revocation takes effect immediately
POST /v1/chat/completions with Bearer key

Responses and streams

Chat responses, longer jobs and status checks fit normal developer workflows.

Responses and streams

One unified schema for responses and streams, via REST and SSE.

REST for request and response
SSE for streams
Status queries for longer jobs

30 daysUsage

Usage made visible

Usage, limits and costs remain traceable in the account.

Usage made visible

The Console reads usage via /v1/usage for 7, 30, 90 days or the full period.

/console/keys: create and revoke keys
/console/usage: usage for 7, 30, 90 days or total
/console/billing: usage and billing in the same account

Four steps to your first response.

You only need one account and one key.

blun.ai · Account

Account

API keys

blun.ai account → Console

To the console

Console · API keys

Name

My first project

Scope

chat

Create a key

Terminal · Request

$ curl https://api.blun.ai/v1/chat/completions \

-H "Authorization: Bearer $BLUN_KEY" \

-d '{"messages":[…]}'

# 200 OK

Console · Usage

Usage

7 · 30 · 90 days

Illustrated workflow. The details are in the documentation.

Who uses the API.

Typical use cases

FOR

SaaS products

Embed BLUN features directly into your own apps.

Your own application

FOR

Agencies

Connect client projects to a controllable AI layer.

Multiple projects

FOR

Internal platform teams

Make models and tools usable via fixed interfaces.

Fixed interfaces

The details.

Collapsed until you need them.

Which endpoints are there?

POST /v1/chat/completions returns responses in completion format and accepts bearer keys with chat scope. /console/keys creates keys, /console/usage reads /v1/usage for 7, 30, 90 days or the full period, and /console/billing shows usage and billing in the same account.

How do keys and permissions work?

Keys are created in your account, given a scope, and deleted again when needed. Revocation takes effect immediately.

What comes next?

King already runs on the BLUN API. Images, voice, and transcription will follow.

Where can I find what?

Docs, login, API keys, usage, and billing are in the same API area with the same sidebar. api.blun.ai is for developers, admin.blun.ai is for administration. Product pages and admin management run separately in their own areas.

Waitlist: no purchase, no charge.

from 19 €per month, annually from 15 € per month

Four plans: Starter, Pro, Pro Max and Enterprise. All prices excl. VAT. All four plans are on the central BLUN waitlist. The complete overview with all features is on the pricing page.

Compare all tiers

ONE ACCOUNT FOR THE ENTIRE WORKSPACE.

One account for everything in chat.blun.ai: Chat and Work, Sites, Code, images, and voice. Sign up for the right plan or start right away with the BLUN API.

Create an API key