kAIxU 6.7 • Developer Docs

Build with discipline.

These docs emphasize production: stable formats, explicit constraints, and deterministic error handling. kAIxU is provided through Skyes Over London LC as a branded intelligence front.

Auth API Key Output Structured Mode Production Models 6.7

API keys

Use a single branded key for authentication. Store it securely and keep it out of client-side code.

Environment variable

Standard key name: KAIXU_API_KEY.

Rotation

Rotate keys periodically and immediately after any suspected exposure.

Environment
KAIXU_API_KEY="YOUR_KAIXU_KEY"

Quickstart

Choose a model, send a request, validate output shape, handle errors.

REST

POST • /v1/generate
curl -X POST "YOUR_KAIXU_ENDPOINT/v1/generate"   -H "Authorization: Bearer $KAIXU_API_KEY"   -H "Content-Type: application/json"   -d '{
    "model": "kaixu-6.7-pro",
    "input": { "type": "text", "content": "Draft an executive summary in 3 paragraphs." },
    "output": { "format": "markdown", "style": "executive" }
  }'

Node.js

Node.js • fetch()
const endpoint = process.env.KAIXU_ENDPOINT;
const key = process.env.KAIXU_API_KEY;

const res = await fetch(`${endpoint}/v1/generate`, {
  method: "POST",
  headers: { "Authorization": `Bearer ${key}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    model: "kaixu-6.7-pro",
    input: { type: "text", content: "Write a product overview in 5 bullet points." },
    output: { format: "markdown", style: "brand-neutral" }
  })
});

if (!res.ok) throw new Error(await res.text());
const data = await res.json();
console.log(data.output?.content);

Request format

Keep requests deterministic with explicit output format and constraints.

JSON shape
{
  "model": "kaixu-6.7-pro",
  "input": { "type": "text", "content": "..." },
  "context": { "policy": "...", "attachments": [] },
  "output": { "format": "markdown | json | text", "style": "executive | operational | technical" }
}

Automation

Prefer json with a schema and validate before downstream execution.

Publishing

Prefer markdown for stability and predictable rendering.

Errors

Handle errors explicitly and preserve request IDs for traceability.

Error shape
{
  "error": { "code": "UNAUTHORIZED | INVALID_REQUEST | RATE_LIMITED | SERVER_ERROR",
             "message": "...",
             "requestId": "req_..." }
}

Production pattern

Validate outputs, log request IDs, and keep keys server-side.