Reference every customer-facing API route on api.kendr.org.

Base rules

• API base domain: https://api.kendr.org.
• JSON endpoints use application/json unless the route is explicitly OAuth form encoded.
• API key auth can be sent as Authorization: Bearer kndr_live_... or X-API-Key: kndr_live_....
• Customer session auth can be sent through the browser cookie, X-Kendr-Session, or an OAuth bearer token with the app scope.
• The machine-readable contracts are GET /api/openapi.json, GET /api/v1/openapi.json, and the versioned public model catalog.

Public discovery endpoints

Browser cookie auth endpoints

App auth and runtime endpoints

OAuth endpoints

Customer wallet and API key endpoints

AI meeting notetaker endpoints

Server integrations can use a scoped Kendr API key to schedule and control the same notetaker lifecycle as the web console. Use meetings:read for list, report, and comment-thread reads, and meetings:write for create, start, stop, delete, and comment mutations.

curl https://api.kendr.org/api/me/meeting-notes \
  -H "Authorization: Bearer $KENDR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"meeting_url":"https://meet.google.com/abc-defg-hij","title":"Weekly review"}'

Governed model gateway endpoints

Model routes accept a Kendr API key with the required model scopes. The standard chargeable routes accept an optional Idempotency-Key — one is generated per request when absent, and a retry that supplies the same key replays settled usage instead of charging twice. All successful generation formats include kendr_usage. Successful managed-route responses also return x-kendr-routing-receipt-id, matching the opaque kendr_routing.receipt_id in the response body or final SSE event.

Shared model request fields include model, input or messages, instructions, max_output_tokens, stream, web_search, tools, conversation_id, response_format, and metadata. Set web_search: false to opt out for one request, or metadata.require_web_search: true when a request must not answer without current web grounding.

Tool calling is server-executed. OAuth app connectors use {"type": "kendr_app", "selection": "auto"} so Kendr can discover the signed-in account's linked apps and retain only those relevant to the request. Custom MCP is a separate contract: pass {"type": "kendr_mcp", "server_id": "mcp_..."} to activate one registered, trusted server. Both require compatible OpenAI Responses routes. See Call remote MCP tools for the full contract.

Cloud KB and hosted vector DB endpoints

Cloud KB routes are the public API for Kendr hosted vector storage. Callers do not upsert arbitrary vectors directly; they create, rebuild, test, and share KBs through these routes while Kendr manages extraction, chunking, embeddings, vector storage, retrieval, reranking, and evaluation history.

App connector and marketplace endpoints

Developer publishing routes under /api/app/developer/skill-packs and /api/app/developer/workflow-packs support private drafts, validation, archive download, and marketplace submission. See Skills and MCP Publishing.

Unified query endpoint

POST /api/v1/query is the execution endpoint. It accepts one surface request and deducts credits only after successful execution.

{
  "surface": "google_search",
  "query": "best llm observability tools",
  "params": {
    "gl": "us",
    "hl": "en",
    "page": 1
  }
}

Where to go next