Give your agent spending power.
Keep the kill switch.
Agent payments are authorized by a revocable ENS capability. Grant, limit, or revoke access on-chain — with changes enforced within seconds.
Live on Sepolia · The Graph v0.0.2 · Hedera HCS 0.0.10456766
GET /service/summarise
402 and 403 mean different things. Paying can satisfy a 402. Nothing satisfies a 403 until the capability is re-granted.
The mechanism
The authorization derives from the name, not the other way around.
Every gate traces back to an ENS ownership assertion. Remove the ENS check and anyone could grant capabilities for names they don't own — the whole system collapses.
The three-chain spine
One capability. Granted, checked, revoked, settled.
Capability as a subname
Grant summarise to alpha.agents.revoke.eth. The grant reverts unless the caller owns the ENS label — authorization, not a label.
Revocation is a state, not a flag
Revoke on-chain and the payment gateway refuses within seconds. A revoked agent gets 403 — no payment amount unlocks it.
Verified from the index
The gateway reads capability status from a subgraph, never RPC, and carries a freshness verdict. Stale index → authorization suspended, not silently trusted.
Three tracks, one causal spine
How each sponsor track earns its place.
ENS — Authorization lives in the name
Capabilities are granted as ENS subname records via CapabilityRegistry.grantCapability(), which reverts unless the caller owns the ENS label in the ENSv2 UserRegistry. Every payment authorization traces back to an ENS ownership assertion — remove ENS and the whole gate collapses.
The Graph — Verified from the index, never trusted
A subgraph indexes CapabilityGranted / CapabilityRevoked events on Sepolia. The gateway reads capability status from The Graph — never direct RPC — and carries a freshness verdict (indexed block vs chain head). A stale index suspends authorization rather than silently trusting it.
Hedera — Settled, with an auditable receipt
On a valid paid request the settle service executes an ERC-3009 transfer on the Hedera testnet EVM, then writes an audit receipt to a Hedera Consensus Service (HCS) topic. Every settlement leaves a publicly verifiable record on the mirror node.
Grant a capability. Revoke it live.
Pay → revoke → same payment fails. Under 60 seconds, on camera.