API reference
Versioned REST over the ownership graph.
The surface below is the shape of the API. Full request and response schemas publish with the API itself, so this page can never describe an endpoint that does not exist.
| Method | Path | What it returns |
|---|---|---|
| GET | /v1/assets | List assets, filtered by entity, brand, class or package membership. |
| GET | /v1/assets/{id}/relationships | The typed edges from an asset, with effective dates and verification status. |
| GET | /v1/assets/{id}/chain-of-title | The resolved path from creator to current owner, with evidence references per step. |
| POST | /v1/assertions | Record a claim with its source evidence. Arrives as proposed; verification is a separate, permissioned act. |
| POST | /v1/evidence | Attach a document version and receive its content hash. |
| GET | /v1/packages/{id} | A Brand Asset Package with its members and each member's owner. |
| GET | /v1/packages/{id}/ibom | The Intangible Bill of Materials for a package, as a structured manifest. |
| GET | /v1/readiness/findings | Open findings, scoped by brand, entity, package or rule. |
| POST | /v1/scenarios | Create a transaction scenario over a snapshot. Never mutates the live graph. |
Authentication
Tokens are scoped to a tenant and carry the same object-level permissions as the user or service that issued them.
Idempotency
Write requests accept an idempotency key. A retried create returns the original record rather than a duplicate.
Versioning
Breaking changes arrive as /v2. The current version keeps working until it is formally deprecated with notice.
The object model behind these endpoints is described under Developers.
Build the ownership record before somebody asks for it.
Register what exists, connect the relationships, attach the evidence. The answer you need under deadline is the one you maintained beforehand.
Evidence-backed relationships Multi-entity by design Built for transfer and diligence