KROG
🇳🇴

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.

Available todayConsent API
Example POST request to the KROG Consent API recording a consent event, returning an ISO 27560-shaped consent receipt.
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.

One worked example

The same object, through the whole chain.

Process, Records, Engine and Agents do not each describe a different example. They describe different stages of the same object: one consent under the Email Newsletter specification.

Object: Consent · sub_8f3c1a · DPS Email Newsletter (6d79e35089c96073)

  1. DPS
  2. Applicable rule
  3. Jural stateStatus: Roadmap
  4. AuthorityStatus: Roadmap
  5. Agent action
  6. Record
This page

Agent action

Status: Roadmap

The act, within given bounds.

An authorised agent acts within its authority: recording a given consent, or halting processing when consent is withdrawn. Writing to the Consent API is operational today; the agent's automated decision against a full jural state is not.

← Previous stageAuthorityStatus: RoadmapWhat the actor has authority to do in this context.Next stage →Status: LiveRecordThe proof, verifiable outside the platform.

Stages labelled Roadmap are designed, not operational today. They are never described in the present tense.