API reference

BEZ Intelligence API

One gateway for every AI capability in the ecosystem. Requests are routed to the best available model for the task, failed over automatically, rate limited per key and logged for audit.

Get an API key Documentation home

Authentication

Bearer keys, scoped to an organisation

Create a key in the developer portal. Keys are hashed at rest, bound to one organisation, carry scopes, and enforce a per-minute rate limit plus a monthly quota. Never ship a key in browser code — call the gateway from your server.

Authorization: Bearer $BEZ_API_KEY
Content-Type: application/json
X-BEZ-Product: your-app        # optional, used for usage attribution

Base URL https://zentechlimited.com. All endpoints accept CORS preflight and return { data } on success or { error: { code, message } } on failure.

Endpoints

Every route the gateway exposes

Text generation through the BEZ Intelligence router. The gateway selects a model per task, fails over automatically and returns the model that actually served the request.

POST/api/public/ai/chatBearer API key

Multi-turn conversation with routing, caching and failover.

Request parameters for /api/public/ai/chat
Field	Type	Required	Description
messages	Message[]	Yes	Ordered turns: { role: 'system' \| 'user' \| 'assistant', content: string }.
system	string	No	System instruction prepended to the conversation.
task	string	No	Routing hint — chat, reasoning, coding, extraction, summarisation.
temperature	number	No	0–2. Defaults to the model profile.

Request

curl https://zentechlimited.com/api/public/ai/chat \
  -H "Authorization: Bearer $BEZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "task": "reasoning",
    "messages": [
      { "role": "user", "content": "Summarise this quarter'"'"'s pipeline risk." }
    ]
  }'

Response

{
  "data": {
    "text": "Three deals carry 62% of forecast value…",
    "model": "bez-reason-1",
    "provider": "bez-self-hosted",
    "usage": { "input_tokens": 412, "output_tokens": 188 }
  }
}

POST/api/public/ai/completionsBearer API key

Single-prompt completion. Convenience wrapper over /chat.

Request parameters for /api/public/ai/completions
Field	Type	Required	Description
prompt	string	Yes	The instruction to complete.
system	string	No	System instruction.
task	string	No	Routing hint.

Request

curl https://zentechlimited.com/api/public/ai/completions \
  -H "Authorization: Bearer $BEZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "prompt": "Write a renewal email for an expiring contract." }'

Response

{ "data": { "text": "Hi Ada, your contract renews on…", "model": "bez-lm-1" } }

POST/api/public/ai/buildBearer API key

One-pass software generation: PRD, architecture, database, APIs, UI, dashboard and timeline. Streams newline-delimited partial JSON.

Request parameters for /api/public/ai/build
Field	Type	Required	Description
prompt	string	Yes	What the software should do.

Request

curl -N https://zentechlimited.com/api/public/ai/build \
  -H "Authorization: Bearer $BEZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "prompt": "A tenant onboarding platform for Lagos property managers" }'

Response

{ "name": "...", "prd": { … }, "architecture": { … }, "database": [ … ], "api": [ … ] }

POST/api/public/ai/studioBearer API key

Creation Engine modules — design, video, social and domain briefs streamed section by section.

Request parameters for /api/public/ai/studio
Field	Type	Required	Description
module	'design' \| 'video' \| 'social' \| 'domain'	Yes	Studio module to run.
fields	Record<string,string>	Yes	Answers to the module brief fields.

Request

curl -N https://zentechlimited.com/api/public/ai/studio \
  -H "Authorization: Bearer $BEZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "module": "design", "fields": { "brief": "Launch flyer for a Lekki development" } }'

Response

{ "name": "…", "summary": "…", "brand": { "palette": [ … ] }, "concept": [ … ] }

Errors & limits

Fail predictably, retry safely

Every failure returns the same envelope. Retry 429 and 503 with exponential backoff and jitter; never retry 400 or 403 without changing the request.

BEZ Intelligence API error codes
Status	Code	Meaning
400	invalid_request	A required field is missing or malformed. The message names the field.
401	unauthorized	Missing, invalid or revoked bearer API key.
403	scope_denied	The key is valid but lacks the scope for this endpoint.
429	rate_limited	Per-minute rate limit exceeded. Retry with exponential backoff.
429	quota_exhausted	Monthly quota for the key is spent. Raise the quota in the portal.
503	no_model_available	No model in the routing chain is deployed and healthy for this task.
500	internal_error	Unexpected gateway error. Safe to retry once.

Streaming endpoints (/build and /studio) return newline-delimited partial JSON — read the body as a stream and parse incrementally rather than awaiting the full response. Back to documentation.