Institutions & civic stewards

Dataset Passport onboarding

Institutional-grade dataset registration, policy binding, and guardian distribution for stewards who need to prove custody.

Connection

Requests hit the SOVEREIGN\PROVENANCE API directly. Bring your own API key and tenant to test in staging. Each step includes the canonical payload you can tweak.

0 of 4 complete

  1. 01 Create institutional steward identity
  2. 02 Issue dataset passport
  3. 03 Anchor dataset event to the ledger
  4. 04 Publish passport via Guardian Node

Live ledger stats appear here once artifacts, nodes, or synthetic activity exist for this tenant. Connect a staging key to load them.

Step 01

Create institutional steward identity

Register the institution, city department, or research lab that will maintain the dataset passport.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.

Step 02

Issue dataset passport

Describe dataset lineage, storage targets, and Accord rights. This issues the Dataset Passport referenced by labs and Guardian Nodes.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.

Step 03

Anchor dataset event to the ledger

Write a ledger event referencing the passport + hash so downstream nodes can verify the dataset state.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.

Step 04

Publish passport via Guardian Node

Broadcast the dataset passport and integrity score to civic portals or lab subscribers.

Waiting

HTTP request

POST
Read docs →

Payload

Response

Response will appear here after you run this step.