OpenPermit
The authorization layer for machine payments

Give AI agents permits,
not wallets.

Your agents buy data, compute, APIs, and products through smart-account x402 mandates you approve, audit, and can revoke at any time. The buyer keeps the same funded wallet. OpenPermit never holds private keys.

Launch AppRead the spec
Challenge typessmart-account x402 live · MPP and gateway adapters next
agent: research-bot-04 · live
12:04:11GET market-data.feed/q3 · $0.04ALLOW
12:04:13x402 settle · monad-usdc · receipt #8841PAID
12:05:02POST gpu.run/inference · $1.20ALLOW
12:05:08ERC-1271 check · smart account readyREADY
12:05:24MetaMask ERC-7715 permission · activeACTIVE
12:05:40GET shadow-api.xyz/dump · $9.00DENY
seller not in mandate allowlist
mandate 0x7c4e…91afsmart-account ready · revocable
Policy before payment

Every machine payment passes through the gate

Agents request. Mandates decide. Smart accounts sign. Receipts prove. One policy layer for x402 on Monad testnet today, with MPP and gateway adapters next.

agentresearch-04agentops-pilotagentbuyer-swarmPERMITpolicy · budget · auditlivex402 / monadnextmpp adapterlivesmart account
allowdenyescalaterevoke · fail closed
01

One layer, three surfaces

buyers, sellers, and the agents in between
buyer/

Buyer Control Plane

  • Issue mandates: budgets, sellers, payment challenge types, expiry
  • Approve MetaMask ERC-7715 spend permissions from the funded wallet
  • Issue x402 ERC-7710 credentials only after readiness checks pass
  • Track spend by agent, seller, payment challenge type, and window
  • Revoke instantly and agents fail closed
  • Export receipts and audit events for finance
mandate 0x7c4e…91af · ACTIVE · revocable
seller/

Seller Platform

  • Drop-in x402 challenges for any HTTP server
  • Emit buyer setup actions with payee, token, chain, seller, and resource metadata
  • Set canonical per-resource pricing and fee quotes
  • Require minimum assurance levels per resource
  • Issue receipts and refunds
  • Revenue analytics from recorded receipts
402 Payment Required → 200 OK
sdk/

Agent SDK

  • Readiness and continuation APIs let generic agents finish checkouts
  • wrapFetch remains available for direct SDK flows
  • MCP and gateway adapters on the roadmap
  • Dry-run price discovery before money moves
  • Policy-aware retries with readable failure reasons
  • Receipts attached to agent traces
continue({ mandateId, checkout })
02

Assurance is a spectrum. Price it in.

every mandate approval gets a trust tier
  1. L1softwareApprovedAPI key, service account, or software-only signer, for local test flows.
  2. L2passkeyApprovedWebAuthn passkey ceremony tied to the OpenPermit relying party.
  3. L3walletApprovedWallet signature without verified hardware context.
  4. L4hardwareWalletApprovedKnown hardware-wallet flow, such as Ledger or Trezor signing.
  5. L5hardwareAttestedVerifiable device identity, firmware capability, or equivalent remote attestation.
  6. L6enterpriseApprovedEnterprise SSO/MFA with organization roles and audit context.

// sellers can require a minimum assurance level per resource; requests below the bar are denied before money moves

03

Why now

the window for an open authorization layer
// the machine economy needs paperwork

PERMITS,NOT WALLETS

01

Agents are already buying

Data, compute, model calls, and APIs, all bought machine to machine with no human checkout in the loop.

02

Payment challenge types exist, control doesn’t

x402 makes resources payable over HTTP; smart accounts make delegated authorization possible without moving funds. They still need authority, spend limits, readiness, and revocation.

03

Audit is the product

Finance and security teams need receipts, policy decisions, and kill switches, not another custody layer.

04

From spec to network

the rollout plan, phases 0–5
  1. phase/0

    Specification & threat model

    Canonical mandate, intent, proof, and receipt formats; fail-closed revocation semantics.

  2. phase/1now

    Smart-account x402

    MetaMask ERC-7715 permissions, x402 ERC-7710 credentials, readiness gates, continuation checkout, receipts, and revocation.

  3. phase/2

    Seller integrations

    Canonical SDK setup actions, payee/token metadata, per-resource assurance, refunds, webhooks, and seller analytics.

  4. phase/3

    Additional rails

    MPP provider adapter, HTTP gateway, Permit2 upto support, and broader smart-account wallet compatibility.

  5. phase/4

    Enterprise controls

    Roles, dual approval, SSO/MFA, SIEM export, and emergency kill switches.

  6. phase/5

    Seller network

    Verified directory, public receipt verification, and marketplace publishing.

The machine economy needs paperwork. We’re writing it.

Request the deckLaunch App
path-neutral · wallet-neutral · fail-closed