> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usealmanac.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Handles, IDs, and paths

> Use the right Almanac identifier at each product boundary.

Almanac uses human identifiers at interactive edges and opaque IDs at direct API
edges.

<div className="almanac-diagram" tabIndex="0">
  <img src="https://mintcdn.com/almanac-e141534d/PSPQxvCsHo2cfSd-/images/diagrams/identifier-boundary.svg?fit=max&auto=format&n=PSPQxvCsHo2cfSd-&q=85&s=f0e2fcbade172b7448ba9f86cdb8eca6" alt="The CLI, SDK, frontend, and MCP resolve a workspace/wiki handle, while direct REST paths require opaque resource IDs." width="1440" height="460" data-path="images/diagrams/identifier-boundary.svg" />
</div>

| Value        | Example                 | Used by                                |
| ------------ | ----------------------- | -------------------------------------- |
| Wiki handle  | `acme/company-handbook` | CLI, Python SDK, frontend, MCP         |
| Workspace ID | `workspace_123`         | Direct REST paths and query parameters |
| Wiki ID      | `wiki_123`              | Direct REST paths and SDK internals    |
| Job ID       | `job_123`               | Exact job reads and waits              |
| Source ID    | `source_123`            | Direct source record reads             |
| Page path    | `operations/onboarding` | Page read and provenance routes        |

Page paths are extensionless and folder-aware. Do not add `.md`, `wiki/`, or
`README.md`. Direct API parameters named `{*_id}` do not accept handles or slugs.

See [Create and link a wiki](/guides/create-select-wiki) for interactive scope and
[Call the REST API](/api/overview) for ID discovery.