Published packages · npm provenance

Connect an AI agent without handing it a wallet key.

Start with read-only capsule discovery and exact, unsigned policy preparation. Neither package signs or broadcasts, and neither can widen the authority your wallet or Safe creates.

See the packages Request an authority map

Published surface

Prepare and inspect. Never sign or send.

Package publication and the production simulation route are separate gates. Exact simulation is deployment-gated and fails closed when its provider or durable quota is unavailable.

TypeScript SDKRegistry

@openzaps/sdk@0.1.0

Compiles the exact Solidity policy tuple, hashes it, prepares unsigned EIP-712 data, and requests block-pinned simulation. Its client has no signing or transaction-broadcast method.

npm install @openzaps/sdk@0.1.0

Inspect SDK source

Read-only MCPRegistry

@openzaps/mcp@0.1.0

Gives compatible agent clients capsule and intent discovery plus block-pinned simulation. It cannot sign, publish, relay, fund, revoke, or broadcast a transaction.

Client config

{
  "mcpServers": {
    "openzaps": {
      "command": "npx",
      "args": [
        "-y",
        "@openzaps/mcp@0.1.0"
      ]
    }
  }
}

Inspect MCP source

Authority map

The agent gets visibility, not a blank check.

One-shot Zaps cannot be connected. Executor pinning applies only to standing recurring, relative, or triggered intents that already name the eligible submitting address.

The owner creates authority

Your wallet or Safe reviews the route, funds the capsule, and signs any standing intent. The Agent Kit never receives the owner key or signature authority.

The policy freezes the terms

Target, adapter, recipient, asset, amount, calldata shape, cadence, output limits, and executor eligibility remain inside the immutable capsule or signed intent.

A separate executor may submit

For a standing recurring or triggered intent, a separately operated executor may submit a due run. It cannot widen the terms, move early, repeat a run, or reach funds outside the capsule.

Discovery is not authority.

Capsule and profile reads are chain-derived. Relay-listed intents and connections may be stale and are not proof of current onchain authority. Verify the capsule, lineage, executor field, and current onchain state before treating a run as eligible.

Read the connection model

Start with a policy sketch

Show us one workflow. We’ll map the agent’s exact limits.

Describe the trigger, target, asset, amount, recipient, cadence, and failure limits. Never share a private key, seed phrase, signature, wallet balance, or signing authority.

Request a Zap Ask in Discord

Pre-audit software. OpenZaps contracts are live on Robinhood Chain with real funds and have not been externally audited. The Agent Kit itself cannot sign or broadcast, but that does not make live contract use risk-free. Verify the package version, provenance, current onchain state, and exact policy before signing. Onchain actions are irreversible.