flowchart LR
accTitle: From a licence to publisher content
accDescr: An application consults the licence, requests temporary authorisation, and presents the token directly to the publisher.
A[Your application] --> B[Check licence and permitted use]
B --> C[Request access token]
C --> D[Publisher checks token]
D --> E[Receive content]
The licence and the token have different roles
The licence defines what you may do. The token lets the publisher check a particular request for a limited time. Content is delivered by the publisher.
Connect your licences
Add your agreements to one library. The publisher confirms the rights before your agents can use them.
Open the workspace, create an organisation and add your existing licences to its library. Identify the publisher, resources and agreement reference. A declared licence remains pending until the publisher confirms it. Free service access does not make publisher content free.
Where a publisher offers terms for acceptance on AssetRouter, accept those terms and satisfy any additional conditions. If payment is required, pay the publisher directly and wait for confirmation. Uploading an agreement or requesting a token is not proof of payment.
Connect an application
Choose MCP for your AI tools, or the API for your own application. Both use the same permissions.
Create a credential for your organisation and store the secret securely on your server. It identifies the organisation authorised to request access; it does not independently prove which individual AI agent is running.
The public API is the primary integration interface. MCP, the protocol used to connect AI tools to external services, calls the same API. Your application or integrator remains responsible for connecting the service to your knowledge base or workflow.
Request and use access
Your agent requests a temporary token, then presents it to the publisher to retrieve the content.
Request access to a specific resource for the use your licence permits. A token is a temporary access credential, not the licence itself. Respect its expiry (the token response uses expires_in) and request another when necessary. Renewal does not automatically mean buying another licence.
Present the token to the publisher’s server. It checks the authorisation before delivering protected content. The licence server does not host or download the publisher’s content for you. A refused or expired authorisation must not be treated as permission to bypass the publisher’s controls.
Read your records
See which requests were authorised. The register records permissions, not what a model subsequently did.
Your workspace shows your licences and the requests and authorisations belonging to your organisation. An authorisation proves the service granted access under the recorded conditions; it does not prove a successful download or later use in a model response. The register is not public.
Use the API reference for integration and the resource-server contract to understand checks at the publisher. The publisher guide explains the other side.