Built for agents
Records readable — and actionable — by machines.
Records are machine-readable across open vocabularies: DPV, ODRL, PROV-O, and Verifiable Credentials. Authorised AI agents can read the jural state and act within the authority they have been granted — auditably.
Your records are readable and actionable by machines — within bounds you set.
POST /v1/consent/records
Content-Type: application/json
{
"data_subject": "sub_8f3c1a",
"controller": "krog.example/controller/acme",
"purposes": ["analytics.product_usage"],
"legal_basis": "consent",
"consent_status":"given",
"policy_uri": "https://acme.example/privacy#v3"
}View response
→ 201 Created
{
"receipt_id": "rcpt_01HV9Z…",
"data_subject": "sub_8f3c1a",
"controller": "krog.example/controller/acme",
"purposes": ["analytics.product_usage"],
"legal_basis": "consent",
"consent_status": "given",
"timestamp": "2026-06-16T09:41:22Z",
"signature": "ed25519:…"
}Consent infrastructure powered by Signatu
On our roadmapJural-state query
In the next stage, authorised agents will query the full jural state and receive a decision of permit · deny · null.
null means the act is competence-invalid — outside the actor's authority (ultra vires). That distinction, between an act that is forbidden and an act that has no legal effect at all, is what separates jural-state querying from a plain policy engine.