Use the free Apache-2.0 SDK and MCP server for sovereign crypto. Use hosted governance when you need public records, API-keyed mint/verify routes, attestation receipts, ledgers, billing, and audit exports.

Use everything

AgentEnvelope has three practical surfaces. Start with the one that matches where your code runs, then add governance when you need operated records, attestation receipts, and audit evidence.

SDK

Use in your own app, worker, Lambda, verifier, or sovereign runtime.

Derive capabilities, sign actions, verify signatures, build delegates, and verify receipts without a network call.

MCP

Use when an agent tool host needs AgentEnvelope as a callable tool.

Expose sovereign verification plus governance and attestation actions to MCP clients such as Claude, OpenAI agents, LangChain, CrewAI, Cursor, or custom runtimes.

Governance + attestation

Use agentenvelope.io when you want operated records and auditability.

Publish public records, call API-keyed verify and mint, receive attestation receipts, keep ledgers, meter usage, and export audit evidence.

common paths

Build offline

Use the SDK directly. Hold your own root, derive capabilities, sign actions, and verify locally. No account or API key.

Use an agent host

Run the MCP server. The agent host calls AgentEnvelope tools instead of embedding SDK code directly.

Operate with governance

Use the portal and hosted API. API keys meter governance routes; signatures, public records, and attestation receipts prove authority.

Mix both

Use the SDK for local authority and governance for records, attestation receipts, ledgers, usage controls, and team continuity.

The governance service adds operated records, attestation receipts, API-keyed routes, ledgers, billing, and audit exports. It does not become the source of authority. The SDK and MCP server remain usable offline; governance is optional.
SDK
npm install agent-envelope-sdk@latest
MCP
npx -y agent-envelope-mcp@latest