API & MCP

Headless by design. Your agents get the whole graph.

Use the REST API, subscribe to webhooks or connect your agents to a hosted MCP server. Bring the graph to the tools your team already uses.

Get API access →See the MCP tools ↓

{
  "mcpServers": {
    "regulation-layer": {
      "url": "https://mcp.regulationlayer.com",
      "auth": "oauth"
    }
  }
}

Illustrative configuration. Access and connection details are confirmed during onboarding.

Hosted MCP server

Tools your agents can call.

Designed to respect the connected user’s permissions. Tool calls remain attributable in the customer record.

get_dial

Read the organisation, department or lens dial, including pass rates and due items.

list_issues

Filter open issues by owner, severity and age.

get_evidence_pack

Retrieve a permitted pack with its obligation, data and approval.

verify_record

Check the signature and chain position of a shared record.

REST API

Every object on the graph, one request away.

Jurisdictions, authorities, regulations, obligations, controls, runs, issues and evidence, with their relationships.

GET /v1/obligations?jurisdiction=US-NY&layer=guidance
Authorization: Bearer <access-token>

{
  "data": [
    {
      "id": "GENIUS.Redemption",
      "synthetic": true,
      "controls": [
        "C-RED-03"
      ],
      "status": "passing",
      "latest_evidence": "EV-2026-10-4472"
    }
  ]
}

Webhooks

Know the moment something moves.

Illustrative webhook events
Event	Meaning
change.detected	A relevant rule or guidance changes.
obligation.updated	An obligation is added or amended.
control.failed	A control run does not pass.
decision.approved	A named owner approves a decision.
evidence.sealed	A new evidence pack joins the customer chain.

{
  "id": "evt_demo_001",
  "type": "evidence.sealed",
  "synthetic": true,
  "data": {
    "evidence_id": "EV-2026-10-4472",
    "chain": "mintwell-private"
  }
}

All API responses, payloads, identifiers and numbers shown here are synthetic examples. These are illustrative contracts, not live endpoint guarantees.

Set up with you

Build the pipelines with your team.

Week 1

Map your sources

Connect systems to the controls they evidence.

Week 2

Stream the first controls

Run priority controls on synthetic data and seal the first packs.

After

Hand over the keys

Your team owns the integrations, pipelines and agents.

Read /llms.txt →

API reference: coming soon. Request pilot access for the current contract.

See your own dial in two weeks.

We scope the library to your business and run it on your synthetic data.

Request early access →