Build with the IGL API Transform Identity into Governed Intelligence

API reference OpenAPI 3.1 · v0.2.0

What changed in v0.2. The MCP governance model is now in the REST contract. A new Projection service adds purpose profiles (GET /purposes), caller resolution (GET /identities/me), purpose-bounded projections with node budgets and a per-node gate explanation, obligations carrying attested or proposed status, read-only consent records, and interaction records (POST /audit/interactions). Every intelligence request accepts a purpose. The 34 v0.1 paths are unchanged.

Proposed API contract for Identity Governed Logic (IGL). The API exposes governed identity, authority, knowledge, policy, evidence, outcome, graph, query, research, agent, workflow, and audit services. It is model-agnostic: reasoning providers can be changed without changing the governed intelligence contract. Version 0.2 adds purpose-bounded projections: purpose profiles, identity projections with per-node gate explanations, obligations with attestation status, caller resolution, consent records, and interaction records, so applications and model callers share one governance model.

The contract covers 42 paths, 46 operations, 63 reusable schemas and 3 webhooks. The source of truth is the specification file itself: igl-openapi-v0.2.yaml (v0.1 kept for comparison).

Authentication, tenancy and conventions

OAuth 2.0 client credentials for workloads and authorization code for user-delegated access; an API key header is accepted on write endpoints that list it. Every governed call carries the tenant boundary header.

Errors use application/problem+json (RFC 9457): type, title, status, traceId and optional field-level violations. 403 means the action was denied by authority or policy; 422 means the request was valid but could not be governed or executed; 429 carries Retry-After. Lists page with cursor and limit (max 200) and return page.nextCursor / page.hasMore.

# governed query from WellSite: obligations due in the next 30 days
curl -X POST https://sandbox.id-me.ai/v1/query \
  -H "Authorization: Bearer $IGL_TOKEN" \
  -H "X-IGL-Tenant-Id: e7bcde63-4ccd-4594-aa64-6de1cce72ae8" \
  -H "Content-Type: application/json" \
  -d '{ "question": "Which obligations are due for this asset in the next 30 days, who owns them, and what evidence is required?",
        "scope": { "assetId": "95dcad56-20a5-4b65-b8e7-6bb3e91510a2" },
        "maxHops": 4, "requireCitations": true, "minimumConfidence": 0.8 }'

Operations by service

Each row is one operation. The scope column is what the token must carry; public needs no credential.

Identity Resolve identities, context, and relationships.

Projection Purpose-bounded projections of an identity: what a caller may see, why, and what was withheld.

Authority Evaluate access, roles, delegations, and decision authority.

Knowledge Create and retrieve governed entities and facts.

Policy Create policies and evaluate governed actions.

Evidence Capture provenance, citations, corroboration, and findings.

Outcomes Record decisions, actions, measurements, and feedback.

Graph Traverse and manage governed graph relationships.

Intelligence Run governed queries, research, crosswalks, and investigations.

Agents Register and invoke governed agents.

Workflows Define and run governed workflows.

Audit Retrieve immutable activity and runtime receipts.

System Service health and capability discovery.

Webhooks

IGL calls your endpoint; reply 200 or 202. Payloads reuse the public schemas.

Examples from the specification

POST /query — WellSite · obligations due on an asset

{
  "question": "Which obligations are due for this asset in the next 30 days, who owns them, and what evidence is required?",
  "actor": {
    "identityId": "b9d4507a-36ce-4d1b-970d-d85797141ff7",
    "organizationId": "e7bcde63-4ccd-4594-aa64-6de1cce72ae8",
    "roleIds": [
      "07e7a6c8-30aa-4a22-85ba-61c3f024e401"
    ]
  },
  "scope": {
    "assetId": "95dcad56-20a5-4b65-b8e7-6bb3e91510a2"
  },
  "filters": [
    {
      "field": "dueDate",
      "operator": "between",
      "value": [
        "2026-10-06",
        "2026-11-05"
      ]
    }
  ],
  "maxHops": 4,
  "requireCitations": true,
  "minimumConfidence": 0.8
}

POST /crosswalk — TortGraph · matter-independent silica crosswalk

{
  "question": "Map the relationships among sites, products, manufacturers, witnesses, experts, and treaters.",
  "scope": {
    "matterIndependent": true,
    "domains": [
      "toxic-tort",
      "silica"
    ]
  },
  "filters": [
    {
      "field": "relationship.status",
      "operator": "in",
      "value": [
        "proposed",
        "certified"
      ]
    }
  ],
  "maxHops": 6,
  "asOf": "2026-10-06T00:00:00Z",
  "requireCitations": true,
  "minimumConfidence": 0.65
}

Schemas (63)

Required fields are marked; enumerations are listed inline. Status enumerations (seed → proposed → certified) are the governance ladder: nothing is certified without a human or a rule the organization controls.