Developer preview

One verification interface. Nation-controlled answers.

The production API will authenticate relying organizations, enforce Nation-specific permissions, obtain citizen consent where required, and return signed assertions.

Intended request flow

  1. Relying organization requests tribal_citizenship.
  2. Tribal Verify confirms the organization is authorized by that Nation.
  3. The citizen sees the requested attribute and authorizes the verification.
  4. The Nation Gateway checks the Nation's authoritative enrollment system.
  5. Tribal Verify returns only the approved assertion and audit receipt.
Example assertion
{
  "verified": true,
  "nation": "Cherokee Nation",
  "attribute": "tribal_citizenship",
  "verification_id": "TV-CN-A82F93...",
  "issuer": "Cherokee Nation"
}

Connector strategy

REST / API

Modern Nation-owned and vendor enrollment systems.

Microsoft Dataverse

Power Platform-based Tribal enrollment environments.

SQL Gateway

Nation-controlled read-only connector for custom or legacy systems.

Vendor connectors

Purpose-built integrations for major Tribal enrollment vendors.