01WITHIN THE RULES
Allowed actions move.
The smart account verifies the active policy before the paymaster sponsors execution.
APPROVEDPROGRAMMABLE MONEY FOR PEOPLE + AGENTS
One account.
Two minds.
Give your personal AI the power to pay—without giving up control. You set the rules. It moves inside them.
Sponsored testnet execution · Every action attributed · Explorer evidence included
SHARED IDOWNER + AGENT
ROOT OWNERYou decide.H
DELEGATED AGENTAgent acts.AI
DAILY AUTHORITYSET BY YOU
Policy enforced onchain
LIMITED
BY YOU
BY YOU
HUMAN OWNEDAGENT ENABLEDGAS SPONSOREDTWO CHAINS
THE SHIFT01
YOUR AGENT SHOULDN’T NEED YOUR WALLET.
Autonomy needs
boundaries.
Agents can already think, search and decide. Paying is where trust breaks. A shared payment identity gives an agent enough authority to be useful—and never enough to become dangerous.
AUTHORITY, MADE VISIBLE
Your rules are the product.
Give an agent a budget, a ceiling, a destination and an expiry. Change any rule. End access instantly.
AGENT POLICY
AUTHORITY
YOUR LIMITSENFORCED ONCHAINPAYMENT CAPOwner set
DESTINATIONSApproved only
EXPIRYOwner set
02OUTSIDE THE RULES
Excess requests stop.
Anything outside the policy is rejected before value can leave the account.
BLOCKEDONE EXPERIENCE · TWO NETWORKS
Your identity
travels well.
The account feels singular. Underneath, each network enforces its own verified permissions and sponsored execution.
ARBITRUM SEPOLIA
PAYMENT PATH VERIFIEDAuthenticated agent payment confirmed with sponsored ERC-4337 execution.
ROBINHOOD TESTNET
PAYMENT PATH VERIFIEDSmart-account deployment, mandate installation, and sponsored payment confirmed.
ROUTING CORE PAYMENTS WORK INDEPENDENTLY
BUILT FOR AGENTIC COMMERCE
Small payments.
Real autonomy.
Agents become useful when they can complete narrowly authorized work. The payment identity is designed for machine-speed purchases with human-defined boundaries.
Pay for intelligence
Authorize calls to data, search, inference and specialist model services.
APPROVED SERVICES ONLYBuy compute
Let an agent acquire the infrastructure it needs within an explicit budget.
OWNER-DEFINED LIMITSLicense content
Purchase access to datasets, research and digital assets from approved providers.
ATTRIBUTED EXECUTIONMaintain services
Allow recurring tools while preserving expiry, revocation and recipient controls.
TIME-BOUND AUTHORITYTHE PAYMENT PATH
One request.
Five checks.
The interface stays simple because the authorization path does the difficult work before execution.
Requests
The delegated key signs a narrowly defined payment intent.
Verifies
The smart account confirms the active delegate and owner context.
Inspects
Recipient, value, token, chain and expiry must all match.
Sponsors
The paymaster covers eligible execution under its own controls.
Records
The outcome becomes attributed, inspectable account activity.
SAFETY IS A SYSTEM, NOT A TOGGLE
The agent never gets the master key.
Separate authority
The agent operates through its own delegated key rather than the owner’s credentials.
Enforced boundaries
Critical rules belong in account validation, not presentation-layer settings.
Immediate revocation
The human can terminate delegated authority without moving the account.
Attributable actions
Activity identifies whether the owner or agent initiated each operation.
FOR DEVELOPERS
A payment tool
an agent can understand.
Expose a narrow interface instead of a general wallet. The agent describes intent; the account decides whether that intent is authorized.
ERC-4337SESSION AUTHORITYSPONSORED GASMULTI-CHAIN
payment-intent.json
{
"action": "request_payment",
"recipient": approvedService,
"amount": requestedAmount,
"network": supportedNetwork
}
// Account policy evaluates the intent
authorize(intent, activePolicy)THE CLEAR ANSWERS
Questions worth asking.
Does the agent control the human’s wallet?
No. The intended model uses separate delegated authority with specific conditions. The human remains the root owner.
Who actually pays the network fee?
A configured paymaster sponsors eligible operations. “Gasless” describes the user experience; execution still has a real network cost.
Why support two networks?
It proves that the identity and permission model can remain coherent while each network independently enforces execution.
Is bridging required for every payment?
No. The core design works independently on each network. Rebalancing remains optional and follows the stable payment path.
THE HUMAN KEEPS THE KEYS.