IntentraxRequest Architectural Review
Menu

SDKs and Adapters

Native adapters for the frameworks you already run

npm install @intentrax/sdk — public on npm, Apache-2.0. Six one-command adapters wrap the agent frameworks teams already run — MCP, LangChain, LangGraph, Cursor, and more — plus a generic contract for any custom agent, so each autonomous action produces a signed, replayable Autonomous Execution Proof.

Read the API referenceExplore developersFor Developers

Developer Path

Install the SDK and wire your framework adapter

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.

Install SDKPublic on npm, Apache-2.0 — install it and run the offline init check with no key.Open adapter guideWire MCP, LangChain, LangGraph, Cursor, or a custom agent through the adapter contract.Read the API referenceEndpoint-by-endpoint: the live public verification API plus the review-gated execution contract.Open proof verifierCheck an issued proof, certificate, passport, or proof hash — no account needed.

What this page provides

One-command onboarding

The SDK's adapter init — public on npm today — generates a concrete setup for supported frameworks like MCP, LangChain, LangGraph, and Cursor, or a generic contract for a custom agent; live execution wiring activates with review-gated sandbox keys.

  • MCP and Cursor
  • LangChain and LangGraph
  • Generic custom-agent contract

Read-only MCP server, published

npx -y @intentrax/mcp-server gives any coding agent two safe tools — it never executes, admits, signs, or writes. The public verify tool is keyless and works today; the tenant read tool additionally needs an issued tenant and a production API runtime enabled for that tenant, so it is not yet callable. Setup is documented for ten-plus hosts (Claude Code, Cursor, VS Code, Windsurf, Kiro, Codex, Gemini CLI, Qwen Code, Zed), or install the Claude Code plugin in one command.

  • Keyless public verify, today
  • Tenant read needs an enabled runtime
  • 10+ MCP hosts

Try it offline right now

Both commands run today with no key and no account: the init dry-run previews a full adapter setup, and check-init verifies a generated one entirely offline.

  • npx @intentrax/sdk init mcp --dry-run
  • npx intentrax check-init
  • No key required

Adapters stay in their lane

Each adapter emits an admission envelope and reads the engine's decision; it cannot mutate model, policy, or proof output or access signing keys.

  • No tool execution
  • No output mutation
  • No signing-key access

Custom agents welcome

Any framework binds through the same admission-envelope contract, so a custom agent gets the same signed AEP as a native adapter.

  • Generic envelope contract
  • Same proof guarantees
  • Portable across hosts

Recommended next steps

Read the API reference

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

Read the API reference
// 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