Asset Router
Developer documentation
Start with your organisation and licences in the workspace. Then connect your application through the API or MCP.
flowchart LR
accTitle: From licence to content
accDescr: The customer reads the terms, requests authorization, and retrieves content from the publisher.
A["Read the licence"] --> B["Request a token"]
B --> C["Publisher verifies access"]
C --> D["Retrieve the content"]
Before requesting access
A declared licence remains visible while awaiting confirmation. Only confirmed rights, or an accepted free offer that grants access, can authorize a request.
Publishers configure resources and terms, publish a reference on their website and confirm customer rights. Buyers connect existing licences, create organisation credentials and request access. A declared licence needs publisher confirmation before it enables access.
The public API is the primary interface. MCP connects AI tools to the same API; it does not introduce different licence rules. Keep secrets on your server, respect token expiry and handle refusals explicitly. Organisation credentials identify the customer organisation, not an independently verified individual agent.
Once a licence is saved, your agent can read its recorded resources, uses and verification state through MCP or the API. A pending confirmation remains visible but does not authorize access. For a confirmed right, the agent requests a temporary token for the intended URL and use, then retrieves the content directly from the publisher. A collection identifies a licensed area; its individual document URLs come from the publisher's catalog or your workflow.
A token permits access within its scope and lifetime. The publisher checks it before serving protected content from its own server. AssetRouter records requests and authorisations, not successful downloads or use in model responses. Payment currently happens directly with the publisher. A request, retry or token renewal is not automatically a new purchase.
AssetRouter signs its service records and lets each party export its own data. Basic hosting needs no publisher signing key or local backup installation. Independent storage, external timestamps and emergency recovery are optional paid services requiring advance configuration and testing.