Getting started with the Records Labs API

Programmatic access to your organization's Records Labs knowledge base — answers with citations for grounded claims and published Creations. For interactive assistants (Claude, ChatGPT), connect the MCP server instead of calling REST directly.

The base URL is your workspace origin: https://<your-records-labs-domain>/api/v1.

Three steps to a working integration

Enable an agent for the API. In Settings → Agents, turn on API access for at least one agent. The API only reaches agents you have enabled for it.
Create an API key. In Settings → API keys, create a key with the scopes you need. The secret (sk-live-…) is shown once — copy it. Keys are hashed at rest.
Call the API with Authorization: Bearer sk-live-…:

curl -X POST "https://<your-domain>/api/v1/answer" \
  -H "Authorization: Bearer sk-live-..." \
  -H "Content-Type: application/json" \
  -d '{"query": "What is our return policy?"}'

Discover the API programmatically

GET /api/v1 — a public (no-key) discovery document: every endpoint with the scope + key type it needs, the auth model, and pointers to everything below.
GET /api/v1/openapi.json — the machine-readable OpenAPI 3.1 spec.
GET /api/v1/docs — interactive Swagger UI over the same spec.
GET /api/v1/me — who a key acts as (org, key tier, granted scopes), for "Connected to …" displays.

MCP for interactive assistants

For Claude, ChatGPT, Cursor and other MCP clients, connect the MCP server at /api/mcp instead of calling REST directly — it exposes the same search, retrieve, fetch, answer and ingest operations with OAuth 2.1 sign-in (or a Bearer API key).

Compatibility

The /api/v1 surface is additive-only: endpoints and fields are added, never removed or repurposed; breaking changes would ship under a new version path with a long deprecation window. See the API stability policy article for the full promise, and the API changelog article for what changed when.