Compliance Status API

How consent works

Founders on Klarify Compass+ create an investor share link in FundRaise Mode. The link token is the API credential. Founders can revoke access at any time; expired tokens return 410 EXPIRED.

This is a self-assessment snapshot — not legal advice, not a regulator certification, and not a guarantee of compliance.

Request

curl -s "https://api.klarify.africa/api/v1/compliance-status/{token}" \
  -H "Accept: application/json"

Sample response

{
  "success": true,
  "data": {
    "api_version": "2026-06-18",
    "company": { "name": "Example Fintech Ltd" },
    "scores": {
      "readiness_score": 62,
      "readiness_label": "In Progress",
      "fundraise_score": 58,
      "fundraise_risk_band": "medium",
      "fundraise_risk_label": "Moderate regulatory risk",
      "checklist_completion_pct": 40,
      "checklist_complete": 8,
      "checklist_total": 20
    },
    "licensing": {
      "product_classification": "DAX",
      "product_classification_label": "Digital Asset Exchange",
      "primary_regulator": "SEC_NIGERIA",
      "secondary_regulators": ["CBN"],
      "arip_stage": "formal_application",
      "arip_stage_label": "Stage 3: Formal Application"
    },
    "verification": {
      "last_score_calculated_at": "2026-06-17T12:00:00.000Z",
      "pack_generated_at": "2026-06-16T09:00:00.000Z",
      "pack_verification_hash": "a1b2c3d4e5f67890",
      "share_expires_at": "2026-06-25T00:00:00.000Z",
      "snapshot_at": "2026-06-18T09:00:00.000Z"
    },
    "top_gaps": [
      {
        "title": "AML/CFT Policy Manual",
        "severity": "critical",
        "regulatory_basis": "MLPPA 2022"
      }
    ],
    "links": {
      "human_summary_url": "https://klarify.africa/fundraise/view/{token}",
      "klarify_profile_url": "https://klarify.africa/?ref=compliance-status-api"
    },
    "disclaimer": "…"
  },
  "meta": { "token_status": "active", "view_count": 3 }
}

Rate limits

60 requests per minute per IP per token. Returns 429 RATE_LIMITED when exceeded.

Documentation

• Full API reference (ReadMe)— authentication, errors, changelog, and integration guides
• OpenAPI spec: klarify.africa/openapi/compliance-status-v0.yaml
• AI site index: llms.txt · llms-full.txt

Use with AI agents (MCP)

The Model Context Protocol (MCP) lets Claude Desktop, Cursor, and other agents call Klarify as a tool — no custom curl scripts. Package: @klarify/mcp.

The fastest way to connect is the hosted MCP endpoint — one URL, no install, no clone:

https://api.klarify.africa/mcp

Connect in Claude Desktop

1. Open Settings → Connectors and choose Add custom connector.
2. Set Name to Klarify.
3. Set URL to https://api.klarify.africa/mcp.
4. Save the connector — the Klarify tools appear in your chat.

Connect in Cursor

Add to your project .cursor/mcp.json (or global MCP config):

{
  "mcpServers": {
    "Klarify": {
      "url": "https://api.klarify.africa/mcp",
      "headers": {}
    }
  }
}

Tools

• get_compliance_status — fetch snapshot (requires founder share token)
• get_klarify_api_info — API docs URLs and orientation (no auth)

Agents and UIs that display compliance data must surface the mandatory disclaimer included in every tool response.

Alternative: run from source (Blockspace team)

The stdio package @klarify/mcp runs locally for development. Build from an authorized clone (pnpm --filter @klarify/mcp build), then point your client at it. Claude Desktop — ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "klarify": {
      "command": "node",
      "args": ["/absolute/path/to/klarify/packages/mcp/dist/index.js"],
      "env": {
        "KLARIFY_API_BASE_URL": "https://api.klarify.africa"
      }
    }
  }
}

Need MCP access or have integration questions? hello@klarify.africa · Full MCP setup (ReadMe)