Your content. Your conditions.
Publish licence terms, confirm your customers’ rights and authorize access. Your articles, reports and files stay on your infrastructure.
I publish contentEXAMPLE LICENCE
One source. Three uses.
Industry outlook A report from a publisher
Your AI agent
ai-inputAsset Router✓ Permitted use
PublisherServes the content
The right source, in your answer.
This example licence permits using the report as input. With confirmed rights, the agent requests a token and retrieves the report from the publisher.
Your AI agent
ai-indexAsset Router✓ Permitted use
PublisherServes the content
Make licensed knowledge searchable.
Indexing is also permitted by this example licence. The agent requests authorization for that use; permission to index does not grant permission to train.
Your AI agent
ai-trainAsset Router× Use not permitted
PublisherNo access for this use
A clear boundary is useful, too.
Training is not permitted by this example licence. No token is issued for that use. The customer can discuss different terms with the publisher.
The request and its outcome are recorded. Content stays with the publisher.
Asset Router
One connection. Two sides of knowledge.
Bring premium external sources into your company’s AI workflows. Clear licence terms, controlled access and a record both sides can read.
Your agents. Better informed.
Bring your licences together, see which uses are permitted and connect your agents through MCP or the API. Request content directly from connected publishers.
I need content for AIBUILT AROUND THE ACCESS
From permission to useful knowledge.
Define
The publisher chooses the resources and permitted uses. The customer saves the licence in their library.
Connect
An agent reads the licence and requests temporary access for a specific resource and use.
Retrieve
The publisher verifies the token and serves the content. Both parties can consult the authorization record.
Make knowledge work with AI.
Start with hosted licence management. Add a custom integration when you need one.