One key. Every AI tool.

Quickstart in three steps

1. 1

   Create a key

   Settings > API > Create key. Pick its scopes; you see the secret once.

2. 2

   Store it

   Put it in KLOUDBOARD_API_KEY (a .env file, your shell, or CI secrets).

3. 3

   Connect or call

   Add it to Claude Code with one command, or call any tool over HTTPS.

claude mcp add --transport http kloudboard https://app.kloudboard.com/mcp \
  --header "Authorization: Bearer $KLOUDBOARD_API_KEY"

KLOUDBOARD_API_KEY=kbk_your_key_here

curl https://app.kloudboard.com/api/v1/credits \
  -H "Authorization: Bearer $KLOUDBOARD_API_KEY"

curl -X POST https://app.kloudboard.com/api/v1/tools/generate_audio \
  -H "Authorization: Bearer $KLOUDBOARD_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"capability":"tts","prompt":"Hello from kloudboard."}'

const res = await fetch("https://app.kloudboard.com/api/v1/tools/web_search", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.KLOUDBOARD_API_KEY}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({ query: "best time to post on YouTube" }),
});
const body = await res.json();
if (!body.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
console.log(body.data, res.headers.get("X-Credits-Charged"));

import os, uuid, requests

res = requests.post(
    "https://app.kloudboard.com/api/v1/tools/web_search",
    headers={
        "Authorization": f"Bearer {os.environ['KLOUDBOARD_API_KEY']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={"query": "best time to post on YouTube"},
)
body = res.json()
if not body["ok"]:
    raise RuntimeError(f"{body['error']['code']}: {body['error']['message']}")
print(body["data"], res.headers.get("X-Credits-Charged"))

What one key reaches

Every tool is POST /api/v1/tools/<tool> with its arguments as JSON. GET /api/v1/tools lists them with their schemas; the tool reference has every one.

Authentication and scopes

Send Authorization: Bearer $KLOUDBOARD_API_KEY. A key belongs to one workspace, acts as the member who created it, and stops working when it is revoked or they leave. The same key works as a Bearer header on the MCP server, so headless Claude Code and CI need no browser sign-in.

Credits and pricing

Paid calls hold their estimate in AI credits first, refund what they do not use, and report the charge in cost and the X-Credits-Charged and X-Credits-Remaining headers. Reads are free; get_pricing quotes any plan before you run it. What credits cost is on the pricing page.

Responses and errors

Every answer is { ok, data } or { ok: false, error: { code, message, hint, request_id } } with a real status code and an X-Request-Id header. Switch on error.code.

// 200
{ "ok": true, "tool": "generate_audio", "data": { "asset": { "url": "https://…" } },
  "cost": { "credits": 60, "balance": 12250 } }

// 402
{ "ok": false, "error": { "code": "insufficient_credits",
  "message": "This costs about 60 AI credits and the workspace has 12 left.",
  "hint": "Nothing was charged. Top up AI credits, then retry with the same Idempotency-Key.",
  "top_up_url": "https://app.kloudboard.com/settings?tab=billing",
  "request_id": "req_5f0c6a1b2c3d4e5f6a7b8c9d" } }

Versioning and deprecation

• v1 (/api/v1) is the current, stable version.
• Additive changes (new endpoints, tools, optional fields and error codes) ship without a new version, so clients should ignore fields they do not know.
• Breaking changes ship only as a new version path (/api/v2); the old version keeps working side by side.
• Before an endpoint or version is removed, its responses carry a Deprecation header (RFC 9745) and a Sunset header (RFC 8594) with the shutdown date, at least 6 months ahead, and the changelog announces it.
• A deprecated endpoint keeps working until its Sunset date.