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

> ## Agent Instructions
> The OpenAPI document at /api-reference/openapi.yaml defines the target contract. Its x-reflections-availability field and each operation's availability notice identify supported test and live forms. Do not infer implementation from a schema or code sample. Live keys support account details, reads of the licenses the calling account holds as licensee or issued as talent (GET /v1/licenses?role=issuer), and GET /v1/generations?license=… for the state of outputs under such a license (summaries only: no prompt, reference, bytes or metadata). Live image checks, submissions and receipts are built but not activated: until activation, a live POST /v1/checks or /v1/generations returns 403 live_not_activated, which must not be retried. Discovery and JWKS are at the origin root (https://app.reflections.ai/.well-known/...), not under /v1.
> Three rules hold everywhere: a decision is never an error (deny and escalate are 200 responses, and a live check still evaluating is a 202 with status checking); generate nothing for a named talent without an allow; deliver nothing until the generation is allow.
> The sandbox accepts personal rk_test_ keys. Persist a separate Idempotency-Key and body for each logical /v1 POST; retry an unknown outcome with the same key and body. OAuth and Talent API MCP remain planned.

# Glossary

> Every term in the Talent API, with its counterpart in RSL 1.0, the Human Consent Standard and C2PA.

<Note>
  Protocol vocabulary. Inclusion here does not establish implementation: the current Talent API
  serves only the test-mode operations listed in the sandbox.
  Start with the [runnable quickstart](/quickstart) and [sandbox support matrix](/sandbox).
</Note>

Each term below is used with one meaning across the API and these docs. The last three columns give
the nearest counterpart in [RSL 1.0](/standard/interop/rsl), the
[Human Consent Standard](/standard/interop/human-consent-standard) (HCS) and
[C2PA](/standard/interop/c2pa). A blank cell means that standard has no counterpart. "Closest"
marks a counterpart that covers part of the meaning, not all of it.

## Parties and identity

| Term | Meaning | RSL 1.0 | HCS | C2PA |
| - | - | - | - | - |
| [Talent](/concepts/talent-and-facets) | A person whose name, likeness and voice are protected through Reflections | | Rights subject | |
| [Facet](/concepts/talent-and-facets#facets) | One part of a talent's identity a license can cover: `name`, `likeness`, `voice`, `twin` or `knowledge` | Closest: `<content>`, what a license covers | | |
| [Posture](/concepts/talent-and-facets#posture) | A talent's standing public answers for uses with no license | Closest: a published `<rsl>` document | Declarations for uses | |
| Declaration | One posture answer: `allowed`, `license_required` or `prohibited` | `<permits>`, `<prohibits>` | Allowed, allowed with terms, prohibited | |
| [Atlas](/concepts/atlas) | The identity graph behind resolution: names, aliases, transliterations, confirmed credits and roles, representation, facets | | | |
| Name index | The signed list of every protected talent's names, for matching on your side | | Closest: a registry | |
| [Representative](/concepts/parties#representatives) | An account that acts for a talent under a mandate | | Representative | |
| Mandate | A representative's authority, with named powers such as `review_outputs` | | Closest: a representative's authority | |
| License draft | Terms a representative prepares for a person to sign; it grants nothing | | | |
| [Licensee](/concepts/parties#licensees) | The account that holds a license, such as a brand or a platform | | | |
| [Platform](/concepts/parties#platforms) | The account that generates and calls checks and generations | | | Claim generator and claim signer for its output |
| End user | The person a platform acts for; attributed on checks, never a licensee | | | |
| Connection | A licensee's permission for a platform to use its licenses | | | |
| Account | One object for brands, agencies, studios, platforms and representatives | | | |

## Licenses

| Term | Meaning | RSL 1.0 | HCS | C2PA |
| - | - | - | - | - |
| [License](/concepts/licenses) | A signed agreement between a talent and a licensee | `<license>` | The terms behind "allowed with terms" | |
| License revision | One signed version of a license's terms, which never change | | | |
| Terms digest | `sha256:` over the canonical form of a revision's signed terms | | | |
| Scope | A revision's terms in normalized, snake\_case form | Closest: `<permits>` and `<prohibits>` | | |
| Adjustment | A change to a talent's appearance or context that a license may allow; twelve kinds | | | |
| Protected attribute | Something every output must keep, such as `identity.samePerson` | | | |
| `checked` term | Enforced at a check, a generation or a session sample | | | |
| `recorded` term | Signed and shown, not enforced, such as `conflicts` | | | |
| License request | A licensee's request for a new or wider license; only a signature on the talent's side makes a license | | Clearance | |
| `post_revocation` | What happens to released outputs if a license is revoked: `retain`, `cease_distribution` or `withdraw` | | | |
| Compensation | What the licensee owes the talent | Closest: payment terms in a `<license>` | | |

## Decisions

| Term | Meaning | RSL 1.0 | HCS | C2PA |
| - | - | - | - | - |
| Use | What will be made and how it will be used: `modality`, `kind`, `purpose`, `commercial`, `channels`, `territories` | Closest: the usages in `<permits>` | The use a declaration covers | |
| [Resolution](/concepts/resolution) | Finding which talent a request invokes; it never clears a use | | | |
| [Check](/concepts/decisions) | A decision before generating, `POST /v1/checks` | Closest: an Open License Protocol token request | Closest: clearance | |
| [Decision](/concepts/decisions) | `allow`, `deny` or `escalate` | | Closest: the declaration level | |
| `allow` | Proceed and meet every obligation | `<permits>` | Allowed, or allowed with terms once licensed | |
| `deny` | Do not proceed | `<prohibits>` | Prohibited | |
| `escalate` | Wait: a person with authority decides | | | |
| Reason | Why a use was denied or escalated, in the license's own words | | | |
| Remedy | What would change a `deny` | | Clearance, for `license_request` | |
| [Obligation](/concepts/obligations) | Something a platform must do for an `allow` to hold | Closest: conditions in a `<license>` | Closest: the terms of "allowed with terms" | |
| Authorization | A signed token, `tlp-auth+jwt`, proving a check allowed one exact request | Closest: an Open License Protocol token, type `rsl` | | |
| [Escalation](/concepts/escalation) | A request waiting for a reviewer, with an expiry | | | |
| Reuse | One check covering several generations of the same use for one end user | | | |

## Outputs and proof

| Term | Meaning | RSL 1.0 | HCS | C2PA |
| - | - | - | - | - |
| [Generation](/concepts/generation-checks) | An output submitted for a decision before delivery | | | The asset a manifest describes |
| Finding | The result of one rule on an output: `preserved`, `violated` or `unchecked` | | | |
| Held output | An output waiting for a reviewer to release it | | | |
| Fingerprint | A perceptual hash and face or voice embeddings of an output, used to look it up | | | Soft binding |
| Watermark | A mark you applied and registered on a generation | | | Soft binding |
| [Session](/build/real-time-sessions) | A live voice or video use under short-lived tokens and sampled checks | | | |
| Sample | An audio window, transcript turn or frame from a session | | | |
| [Receipt](/concepts/provenance) | A signed record of a decision, `tlp-receipt+jwt` | | | Carried in the `ai.reflections.license` assertion |
| C2PA assertion | The `ai.reflections.license` assertion holding the receipt | | | An assertion in the manifest |
| Artifact digest | The SHA-256 of an output's bytes, bound into its receipt | | | Closest: a hard binding |
| [Assurance](/concepts/what-we-enforce) | `observed` (Reflections checked it) or `attested` (Reflections recorded what you stated) | | | |
| Verification | Finding and checking the receipt behind a file, manifest or receipt ID | | | Manifest validation |
| Use status | What use of an output is permitted now: `permitted`, `ceased`, `withdrawn`, `expired` | | | |

## Consent and settlement

| Term | Meaning | RSL 1.0 | HCS | C2PA |
| - | - | - | - | - |
| [Revocation](/concepts/revocation) | Every narrowing of consent: a license, a facet, a mandate or all consent | | Closest: a changed declaration | |
| Suspension | A license paused by the talent or a representative, which can resume | | | |
| Acknowledgement | A platform's statement that it did what a revocation requires | | | |
| Revocation feed | `GET /v1/revocations`, the source of truth for every revocation | | | |
| [Usage record](/concepts/usage-and-settlement) | A platform's report of units used by a generation or session | | | |
| Statement | A license's monthly amounts, reconciled against observed use | | | |

## The protocol

| Term | Meaning | RSL 1.0 | HCS | C2PA |
| - | - | - | - | - |
| [Talent License Protocol](/standard/overview) | The open protocol the Talent API implements | Aligns with RSL 1.0 and its Open License Protocol | Aligns with HCS declarations | Aligns with C2PA manifests |
| License server | Holds licenses and decides checks; the Talent API is one | The license server named by a `server` attribute | The server a declaration points to for clearance | |
| Generation tool | A model provider or tool that runs generation and verifies authorization tokens | | | |
| Verifier | Anyone who checks a receipt, such as a distribution platform | | | Validator |
| Human Consent Registry ID | `talent.hcs_subject_id`, when the talent is registered there | | A rights subject's registry entry | |

## Related

<Columns cols={2}>
  <Card title="Terminology" icon="book" href="/standard/terminology">
    Normative definitions in the Standard.
  </Card>

  <Card title="How it works" icon="diagram-project" href="/how-it-works">
    The lifecycle from prompt to receipt.
  </Card>
</Columns>


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