> ## 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
> Every page in this documentation carries a `plans` list in its frontmatter and a page-details table naming the plans its content applies to: `All plans`, or a subset of `Community`, `Team` and `Enterprise`. A page limited to some plans also opens with a plan marker naming them.
> Use [Capabilities and limits](/product-status) for capability entitlements and documented availability and limits, and [Plans and billing](/plans-and-billing) for plan pricing and billing policy. Those pages are canonical; do not duplicate their policy values here.
> Reading this documentation grants no product access and no permission. No agent can create or approve a Nitsor release.

# A request reached a terminal state

> The payload the contract declares for a Request that reached a terminal state.

> [!NOTE]
>
> The product sends no webhooks. The contract declares this event type, but there is no subscription route and no delivery.


## OpenAPI

````yaml /openapi.json webhook dev.nitsor.request.completed.v1
openapi: 3.1.1
info:
  title: Nitsor public API
  version: v1
  description: Generated from the Nitsor API contract; never edit by hand.
  x-nitsor-product-version: 0.1.0
servers:
  - url: https://api.nitsor.com
    description: Nitsor API
security:
  - bearerAuth: []
tags:
  - name: auth
    description: 'Authentication: the session a bearer credential reaches.'
  - name: blind-checks
    description: >-
      Blind checks: scans labelled without seeing the model, scored against it
      under a readiness plan fixed before checking starts. Plan writes need a
      person's own token, and these routes do not accept one yet; an Agent token
      is refused, so change plans on the Pipeline tab meanwhile.
  - name: capabilities
    description: 'Capability discovery: versions, limits and formats.'
  - name: datasets
    description: 'Datasets: named selections over a project''s version graph.'
  - name: decisions
    description: Audit decisions behind authorization refusals.
  - name: executions
    description: Pipeline executions and their work items.
  - name: ledger
    description: Account ledger entries.
  - name: model-label-outcomes
    description: >-
      Model label outcomes: what people did with each label a model proposed,
      per Task and per Proposal.
  - name: model-runs
    description: >-
      Model runs a person starts on Tasks: the estimate to confirm, and the
      start that runs one scan at a time.
  - name: openapi
    description: The OpenAPI description this deployment serves.
  - name: project-groups
    description: 'Project groups: the account''s shared folders on the project shelf.'
  - name: projects
    description: 'Projects: creation and listing.'
  - name: requests
    description: 'Async Requests: status, listing, cancel and the per-item report.'
  - name: service-accounts
    description: >-
      Service accounts and their tokens: the machine identities jobs run as,
      managed by a person holding service-accounts:manage on their own token. A
      secret is shown once, on the answer that created it. A service account's
      access to a project is given, changed and removed by that project's
      admins, with a personal token holding admin there.
  - name: sources
    description: Sources and mask-read presigning.
  - name: storage-connections
    description: >-
      Storage connections to customer object storage, and the
      operator-provisioned credential handles they name.
  - name: task-comments
    description: Task comments, replies and attention.
  - name: taxonomy
    description: Taxonomy definitions, display groups and binding.
  - name: version-graph
    description: Version-graph commits, branches, landmarks and merges.
  - name: workflow
    description: Workflow definition and binding.
paths: {}
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        An Agent credential (`nits_…`), or a person token (`nitp_…`) on a
        deployment that enables them. `GET /api/v1/session` names the principal
        a credential proves.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.