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

# License context: use and territory

> Every run with a licensed Omnichar character states its use and territory. Send license_context with the API; the dashboard asks once per session.

A license covers a use, such as `advertising`, in some territories. The run itself does not say which use or territory it is for, so you state them, and the [license check](https://docs.omnichar.org/api/licensed-characters.md#what-is-checked) compares them with the license.

## With the API

Send `license_context` with every run that casts a licensed character:

```json theme={null}
{
  "slug": "default-flux-2-klein-4b",
  "characters": { "character": { "char_id": "7f1c2a9e-..." } },
  "license_context": { "use": "advertising", "territory": "SE" }
}
```

| Field | Matches |
| - | - |
| `use` | `scope.use`, ignoring case |
| `territory` | one of `scope.territories`, ignoring case; any territory if the license is `worldwide` |

A run with a licensed character and no `license_context` answers `400` with the code `bad_request`, and is not recorded as usage. The same context applies to every licensed character in the run. Runs of your own characters, or of characters nobody licensed, need no context.

## In Omnichar Cloud

The first time you cast a licensed character in a session, the dashboard asks how you will use it, offering only the use and territories the license allows. The answer is saved on the session and shown as a chip beside the character in the dock; select the chip to change it. Each session keeps its own answer.


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