API & MCP Access

Verachi supports API keys, REST-style app endpoints, and a stateless HTTP MCP endpoint.

API keys

1. Open Settings.
2. Go to Security & data.
3. Open API keys.
4. Create a key with the scopes your tool needs.
5. Copy the key when it is shown.

Send API keys as bearer tokens:

Authorization: Bearer YOUR_API_KEY

Revoke keys you no longer use.

Scopes

Scopes are specific. Project or decision scopes do not automatically grant guideline or risk writes.

Examples:

• guidelines:read
• guidelines:write
• risks:read
• risks:write

MCP endpoint

https://app.verachi.io/api/mcp

MCP requests are HTTP-based, stateless, and authenticated with the same bearer token header.

Example:

{
  "mcpServers": {
    "verachi": {
      "url": "https://app.verachi.io/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Current MCP surface

MCP covers automation around:

• decisions
• projects
• documents
• guidelines
• risks
• connection identity through auth_whoami

MCP does not expose chat execution, integration setup, audit administration, notifications, AI settings, organization/team/user management, or API-key management.

REST API

Common app endpoints include:

Use the web app for workspace administration unless you are building against a documented API flow.

Next

• Using Verachi MCP
• Settings