[DOCS]

Authentication

POST /v1/chat/completionsauthenticates with your account's API key in the Authorization header, following the same convention as OpenAI; SDKs handle it automatically via apiKey. GET /v1/models is public and requires no key.

HEADER

curl https://blazeinference.com/v1/chat/completions \
  -H "Authorization: Bearer sk-blaze-..." \
  -H "Content-Type: application/json" \
  -d '{"model": "z-ai/glm-5.2", "messages": [{"role": "user", "content": "hi"}]}'

How keys work

FACT	DETAIL
One key per account	Dead simple: no orgs, no projects, no key juggling.
Format	`sk-blaze-`
Shown once	We store only a hash. Copy the key at creation; it cannot be revealed again.
Replace	A key can be replaced from the dashboard: a new key is issued and the previous key is deleted immediately.
Enable / disable	One switch on the dashboard. Disabled keys reject new requests instantly with api_key_disabled.

Failure modes

HTTP	CODE	WHEN
401	`missing_api_key`	No Authorization header.
401	`invalid_api_key`	Key unknown or malformed.
403	`api_key_disabled`	Key toggled off on the dashboard.