Skip to content
All documentation

How licensing works

The checks that happen before a hosted tool runs.

The licence is not enforced by the instructions in the package. It is enforced by the database, on every call, in one transaction.

  1. 01Verify the OAuth access token: signature, issuer, audience, expiry.
  2. 02Resolve the caller to a user and an organisation from the verified token.
  3. 03Find the licence for that organisation and that skill.
  4. 04Check the licence status and the subscription behind it.
  5. 05Check the tool is entitled, and that the feature is switched on.
  6. 06Reserve the usage for this call, then run the tool.
  7. 07Settle the reservation. A call that failed releases its units; a call that returned an answer keeps them.

What the agent cannot do

The agent names a tool and its arguments. It cannot name an organisation, a licence, a feature or a price. A request that asks for any of those is refused before it reaches the tool.

Access ends when the subscription ends

A cancelled subscription keeps access until the end of the period already paid for. An unpaid, incomplete or expired subscription has no premium access. A revoked licence is refused immediately.