ENS · Hedera x402 · Privy

Not another agent that pays an API. LEASH is the ENS name that can un-pay it.

Bind an external AI agent to a spending policy declared on your ENS name. Cut one resolver record and that agent’s spending dies everywhere — in one on-chain write.

Try the judge sandbox →Open the real console

No login, no wallet, no ETH for the sandbox. Every step runs a real on-chain transaction.

The one-write kill

Revocation is a single resolver write. The agent’s next payment fails closed.

The facilitator we run reads the policy from your ENS name before every settlement. Clear the record and there is nothing left to read — no per-service offboarding, no key rotation, no scramble.

POLICY LIVE

Agent pays, capped per call, on the allowlist.

ONE WRITE → REVOKED

Nothing to read → every future payment denied, everywhere.

How it works

A spend-control plane for agents you don’t own.

  1. Bind

    Attach an existing external agent (its ERC-8004 / EVM identity) to a 2-of-2 co-signed Hedera spending account. Neither the agent nor LEASH can move funds alone.

  2. Declare

    Publish the spend policy on your ENS name: a hard per-call cap, an allowlist, and an optional rolling budget with time-windows.

  3. Enforce

    Our self-hosted x402 facilitator reads that ENS policy before every settlement on Hedera. Gas-free, and it fails closed the moment the record is gone.

How enforcement actually works (the honest version)

This is the corporate-card model, not a trustless one. The chain stores the policy and records the revocation — it does not itself stop a payment. The facilitator we run is the party that reads the ENS-declared policy and enforces it. Enforcement is facilitator-trusted, by design and stated plainly.

Agent identity is on-chain-resolved, not verified — ownerOf tells us who holds the name, not who is in control of the key.

The per-call cap (maxPerCall, read live from ENS) is the hard bound on every settlement. Rolling daily / weekly budgets are a soft budget, tracked across calls, not a hard on-settle cap.

LEASH does not mint agents. It binds agents that already exist. Privy is an independent funding rail that denies over-funding, so a bound agent can only ever hold what its policy allows.

Try the judge sandbox →Open the real console

The sandbox runs the full bind → declare → enforce → revoke path against real on-chain transactions — nothing to install.