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

> ## Agent Instructions
> Nitsor is a pre-release product. Every page in this documentation carries an availability status in its frontmatter (`availability`) and, as the first element of its body, a link labelled `Available now`, `Limited design-partner access`, or `Planned - not available yet`. That label is binding: it says whether a reader can use the behaviour the page describes.
> A page written in the present tense is not a claim that the behaviour ships. Where the availability label says `Planned - not available yet`, the page describes a target contract and there is no runnable product, screen, command, or public interface behind it.
> Every readiness claim this documentation makes lives on the Product status page. If any statement elsewhere disagrees with the capability status matrix on that page, the matrix is correct.
> Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release.

# Reference

> Find the exact interfaces, contracts, deployment controls, and terms that exist today, each stated with its current boundary.

<a className="nit-availability" data-availability="available-now" href="/product-status#status-definitions" aria-label="Available now. Read the status definitions."><span aria-hidden="true" className="nit-availability__dot" />Available now</a>

These pages record what exists, exactly, with the limit that applies to each one. They are deliberately narrow: an interface appears here only when something is implemented and tested, and the boundary is stated beside the capability rather than below it.

## The reference pages

| Page                                                          | What it records                                                                          | Availability                  |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ----------------------------- |
| [Integrations and public interfaces](/reference/integrations) | Every public interface this site offers, and how the documentation reaches an AI tool.   | Available now                 |
| [Public HTTP API](/reference/api)                             | Sixteen implemented routes, the error vocabulary, and the authentication limitation.     | Limited design-partner access |
| [Command-line interface](/reference/cli)                      | Five command families, one tested command sequence, and the distribution boundary.       | Limited design-partner access |
| [Data model and contracts](/reference/data-model)             | The replay-tested event, authorization, version, and workflow contracts.                 | Limited design-partner access |
| [Self-host mechanics](/reference/self-host)                   | What `nitsor up` actually starts, and what a supported product would have to start.      | Planned — not available yet   |
| [Deployment and security](/reference/deployment-and-security) | The verified public-site controls, and the deployment and security questions still open. | Planned — not available yet   |
| [Glossary](/reference/glossary)                               | Thirty-five terms with their definitions and the misreading each one attracts.           | Available now                 |

## What a reference page will not do

A reference page states a contract and its limit. It does not present a request example as runnable unless an end-to-end test executes that exact request against a supported public environment, and no such environment is published. It does not give installation instructions for a package that has no release. Where an example is missing, the page says why.

Documentation, type definitions, and mock examples are useful evidence. They do not replace a test against a released package or service.

## Next step

Open [Integrations and public interfaces](/reference/integrations) for the complete list of what exists, then [Plan an integration](/guides/plan-an-integration) for the evidence to demand before you depend on any of it.

<table className="nit-page-details" aria-label="Page details">
  <tbody>
    <tr><th scope="row">Outcome</th><td>Go straight to the interface you care about and read its boundary before its capability.</td></tr>
    <tr><th scope="row">Availability</th><td>Available now</td></tr>
    <tr><th scope="row">Audience</th><td>Software engineers, Data engineers, Security and platform teams, AI agents</td></tr>
    <tr><th scope="row">Prerequisites</th><td>Read Product status</td></tr>
    <tr><th scope="row">Last verified</th><td>2026-08-23</td></tr>
  </tbody>
</table>