Developers
Ten object types and the edges between them.
The API is a view over the same objects the console uses, under the same object-level permissions. There is no second, more permissive model behind it.
Object model
entityA legal entity: owner, operator, licensor, licensee or counterparty.brandA commercial or internal brand, with an owner and one or more operators.assetAn intangible asset: mark, copyright work, software component, domain, account, dataset or model.packageA Brand Asset Package — an economic grouping of assets and rights.agreementAn executed contract relevant to ownership, rights or restrictions.rightA structured consequence of an agreement: a grant, an obligation or a restriction.personA contributor, officer or reviewer, reconciled across external identities.assertionA claim about a relationship, with status, source evidence and reviewer.evidenceA versioned document or external record supporting one or more assertions.scenarioA modelled transaction over a snapshot of the graph.
Events worth subscribing to
assertion.verifiedA material claim passed human verification — the event most workflows care about.relationship.supersededA new state replaced a previous one; the old relationship remains queryable.readiness.finding.openedA rule raised a gap: no verified owner, uncovered contributor, custody mismatch, expiry approaching.evidence.addedA document was attached to an assertion, with its version and content hash.scenario.approvedA transaction scenario moved to approved, which usually starts work elsewhere.
Integration rules that will not change
- Deliveries are signed, and carry an idempotency key so a retry never creates a second record.
- Imported facts arrive as proposals. An integration cannot promote itself to verified truth.
- Tokens use least-privilege scopes and are rotatable without losing a connection's history.
- Breaking changes ship as a new API version, never as a change to the current one.
Endpoint-level documentation lives in the API reference, and ships alongside the API itself so the two cannot drift.
Building an integration?
Tell us which system and which direction the data should flow. Connector work is prioritised by what customers are actually trying to connect, not by which logo looks best on a page.
Talk to us about integrationsBuild 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