Exec402 Documentation
Exec402 is a decentralized execution layer for agents and dapps, designed to power pay‑per‑action on‑chain workflows across multiple chains and tokens.
Agents or dapps only need to sign lightweight payment authorizations against the Exec canister; a network of executors continuously picks up pending tasks from the canister, settles them on-chain via the ExecCore contracts, and earns a share of the fees.
What you can do with Exec402
- Build 402-style, pay-per-action flows where users only sign a single payment authorization and the Exec canister creates and tracks tasks for you.
- Offer gasless UX – users sign once, executors pay gas on the settlement chain.
- Charge in multiple token standards (EIP‑3009, EIP‑2612, Permit2) across supported chains using a single SDK.
- Run multi-chain agents across chains and DeFi protocols without running your own relayer / facilitator infrastructure.
- Execute batched and atomic contract calls via the multicall handler, so complex workflows either fully succeed or fully revert.
- Share fees between referrers and executors programmatically at the smart-contract level.
Who this documentation is for
- Referrers – dApps, wallets, and services that want to charge users per action and route execution to Exec402.
- Executors – operators who want to pick up tasks and earn a share of protocol fees.
- Protocol researchers – people interested in the execution layer, 402-style models, and fee distribution.
Where to start
- New to Exec402? Read the Introduction.
- Want to see how it works end‑to‑end? Go to Quick Start.
- Need the protocol mechanics? Check Protocol Overview.
- Looking for supported chains (e.g. Base, BSC)? Check Supported Chains.
- Looking for supported token standards? See Permit Types.
- Already building as a referrer? Read the Referrers guide.
- Curious about operators? Read Executors.
- Have questions? Check the FAQ.
Last updated on