# API documentation brief

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Audience and source

Reader and task: ___
Repository revision: ___
API/library versions: ___
Supported environment: ___

## Contract inventory

| Entry point | Required input | Output/error contract | Source location |
| --- | --- | --- | --- |
| ___ | ___ | ___ | ___ |

## Example proof

Example path: ___
Prerequisites and non-secret configuration: ___
Execution command/runner: ___
Expected output basis: ___
Observed output and exit: not run

## Reader review

Reader questions: ___
Broken links or missing steps: ___
Claims still unverified: ___
Licence and attribution notes: ___
Publication destination/owner: ___

## Boundaries

- Choose a host for each stage and verify its tool mapping. Pass evidence explicitly between stages; the listed resources do not automatically configure or invoke one another.

- Context7 supplies reference material; it does not establish what your own application actually implements.

- The agent definition may need host-tool adaptation. Review the upstream skill’s current licence and terms before redistribution.

Workflow: https://undominated.ai/workflows/#document-an-api

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.