AssetRouter
Documentation
Start with the public integration model: catalog discovery, rights checks, entitlement, and retrieval. The production API is opening in stages, so examples are intentionally marked as launch-preview.
Aperçu du lancement
AssetRouter's launch-preview flow starts with a catalog search, checks the rights profile, creates an entitlement, then retrieves the asset through an auditable delivery URL.
GET /v1/catalog/search?q=climate%20briefing
Authorization: Bearer <token>
POST /v1/entitlements
{
"asset_id": "asset_123",
"license_scope": "consultation"
}Aperçu du lancement
Launch API access uses bearer tokens issued to private beta partners. OAuth and self-serve keys arrive after the first marketplace cohort is stable.
Authorization: Bearer assetrouter_live_...Aperçu du lancement
Every asset is evaluated against allowed use, provenance metadata, delivery constraints, and downstream license scope before retrieval.
license_scope: consultation | product_retrieval | resale | training_review
provenance: required
receipt: generatedAperçu du lancement
Retrieval returns metadata first, then a bounded delivery link once entitlement and payment rules are satisfied.
GET /v1/assets/asset_123/retrieve
{
"delivery_url": "https://delivery.assetrouter/...",
"expires_at": "2026-05-01T12:30:00Z"
}Aperçu du lancement
Publisher setup focuses on catalog shape, rights metadata, provenance requirements, payout model, and delivery readiness.
catalog -> rights profile -> provenance review -> delivery test -> private launchAperçu du lancement
AssetRouter is designed around inspectable provenance, clear license boundaries, and auditable access records. Certifications and formal compliance claims will be published only when complete.
provenance_record: inspectable
license_boundary: explicit
audit_record: retained