The item resource

One piece of a space — a documentation page, a blog post, a roadmap card, an incident — and every field it can carry.

{
  "id": "8f4c…",
  "kind": "page",
  "title": "Publish on your own domain",
  "slug": "own-domain",
  "published": true,
  "group": "Guides",
  "updatedAt": "2026-08-18T04:12:09Z",
  "contentHash": "9f86d081884c7d659a2f",
  "deleted": false,
  "sections": { "before": "- A domain you control", "steps": "1. Add it in Settings → Address" },
  "markdown": "# Publish on your own domain\n\n…"
}

Slots have declared meaning

A space's shape says what each slot is called, whether it is asked for, and — where it is unambiguous — what it is for: summary, symptom, resolution, prerequisite, reference, example. Ask GET /api/orgs/{orgId}/spaces/{spaceId}/shape. A retrieval system can weight a resolution above a prerequisite when somebody asks how to fix something, rather than treating a page as one undifferentiated wall of text.

Where a piece is read

url is the address a reader reaches this piece at — the customer's own domain when they have one, a site of theirs next, ours otherwise. Never assemble it yourself: /p/{orgId}/{spaceId}/{slug} is our address, and it is the wrong one for every customer publishing on a domain of their own.

It is null when the space is not public, when the piece is not published, and when the kind of piece has no address of its own — a changelog entry and a status incident are read on the space's own page. Null means there is nowhere to link to. It never means we did not work it out.