Documentation

Intentrax developer documentation

Everything you need to verify and instrument execution assurance — starting keyless, no account required. Verify a live proof in under a minute, add Intentrax to your coding agent, then wire proof generation into your own app.

Verify a proof in your browser

The public verifier is live and keyless. Verify a real published proof right now with no account, or open the verifier and paste any proof, certificate, passport, or trust-asset identifier. To call it from code, see the API reference.

Add Intentrax to your coding agent

The read-only MCP server is published as @intentrax/mcp-server. It gives any MCP-compatible coding agent two safe tools — verify a public proof and read a tenant proof — and never executes, admits, signs, or writes. The command is the same everywhere; only the config file differs. Never commit a key: the public verify tool needs none, and the tenant tool reads INTENTRAX_MCP_API_KEY and INTENTRAX_MCP_TENANT_ID from your environment.

Which tool works today. intentrax_verify_public_proof is keyless and callable right now — no tenant, no account. intentrax_read_tenant_proof additionally needs an issued tenant and a production API runtime that has been enabled for that tenant; until then it is configured but not yet callable. Contact us to have a tenant runtime enabled.

Most hosts — add this block

{
  "mcpServers": {
    "intentrax-readonly": {
      "command": "npx",
      "args": ["-y", "@intentrax/mcp-server"],
      "env": {
        "INTENTRAX_MCP_API_KEY": "${INTENTRAX_MCP_API_KEY}",
        "INTENTRAX_MCP_TENANT_ID": "${INTENTRAX_MCP_TENANT_ID}"
      }
    }
  }
}
HostConfig file
Claude Codeproject .mcp.json (or the plugin below)
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.json
Cursor.cursor/mcp.json
Kiro.kiro/settings/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json
Gemini CLI~/.gemini/settings.json
Qwen Code~/.qwen/settings.json

A few hosts use a different shape. Each block below is copy-ready — the command is always npx -y @intentrax/mcp-server; only the surrounding keys differ. The public verify tool needs no key; the tenant tool reads its key and tenant id from your environment (VS Code prompts for them interactively; Codex passes them through with env_vars).

VS Code (Copilot) — .vscode/mcp.json

{
  "inputs": [
    { "type": "promptString", "id": "intentrax-mcp-key", "description": "Intentrax MCP key" },
    { "type": "promptString", "id": "intentrax-mcp-tenant", "description": "Intentrax tenant id" }
  ],
  "servers": {
    "intentrax-readonly": {
      "command": "npx",
      "args": ["-y", "@intentrax/mcp-server"],
      "env": {
        "INTENTRAX_MCP_API_KEY": "${input:intentrax-mcp-key}",
        "INTENTRAX_MCP_TENANT_ID": "${input:intentrax-mcp-tenant}"
      }
    }
  }
}

Zed — settings.json (context_servers)

{
  "context_servers": {
    "intentrax-readonly": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "@intentrax/mcp-server"],
      "env": {
        "INTENTRAX_MCP_API_KEY": "${INTENTRAX_MCP_API_KEY}",
        "INTENTRAX_MCP_TENANT_ID": "${INTENTRAX_MCP_TENANT_ID}"
      }
    }
  }
}

Codex — ~/.codex/config.toml

[mcp_servers.intentrax-readonly]
command = "npx"
args = ["-y", "@intentrax/mcp-server"]
env_vars = ["INTENTRAX_MCP_API_KEY", "INTENTRAX_MCP_TENANT_ID"]

AgentScope (the Python agent framework) is also supported — its setup lives in the package README. Full per-host detail is in the @intentrax/mcp-server README on npm.

Or install the Claude Code plugin

/plugin marketplace add Intentrax/intentrax-skills
/plugin install intentrax-execution-assurance@intentrax

One command installs the execution-assurance skill and the MCP server together.

Everything here is open source. Browse the intentrax-skills repo on GitHub, or start from the agent toolkit hub (agent-toolkit-for-intentrax on GitHub).

Developer Path

Verify a proof, or add the MCP server — no account

Start with the no-account action that fits this page; a free account opens the console, and the proof-generating sandbox is issued after a short architectural review.

What this page provides

Verify a proof in under a minute (no account)

The public verification API is live and keyless. Look up a published Autonomous Execution Proof by identifier and read the signed verdict as JSON — one request, no key, no account.

  • Keyless public verify API
  • Real signed proof
  • Honest 404 on unknown identifiers

Add Intentrax to your coding agent

The read-only MCP server is published on npm: run npx -y @intentrax/mcp-server, or install the Claude Code plugin. Setup is documented for ten-plus hosts — Claude Code, Cursor, VS Code, Windsurf, Kiro, Codex, Gemini CLI, Qwen Code, and Zed.

  • npx -y @intentrax/mcp-server
  • Claude Code plugin marketplace
  • Config for 10+ MCP hosts

Build with the SDK

npm install @intentrax/sdk — public on npm, Apache-2.0. Generate an admission envelope, wire a framework adapter, and verify or export proofs; live execution wiring activates with review-gated sandbox keys.

  • npm install @intentrax/sdk
  • Framework adapters
  • Verify and export proofs

API reference and concepts

Endpoint-by-endpoint reference for the live verification API and the honestly-gated execution API, plus how admission, execution, and proof fit together.

  • Public verification endpoints
  • Execution API, review-gated
  • Admission to proof, explained

Recommended next steps

Start the quickstart

Start with public developer guidance, then request sandbox access through review.

Start the quickstart
// Verify a real, signed proof — keyless, works right now:curl -s https://verify.intentrax.com/api/public/verify/proof/45f765a0fb5b20de6f73c38d7a94e48c041640af8cb0c3382fa0302ce2c70992"verification_status": "VALID"// npm install @intentrax/sdk

Build toward a reviewed sandbox path

Nothing you do here is published. The docs are public to read; your sandbox work stays private to your account, and production access is review-gated.

Request Architectural Review