1.0 — Connect
Create an Agent Account with a boundary
Connect an agent through MCP and bind it to a human-reviewed policy. The agent gets scoped commerce authority, never your treasury.



Connect an agent. Give it a goal or x402 payment intent. Elypx402 builds the plan, enforces policy, and retains the result with proof.
Bounded — Agents hold a policy, not a treasury. No seed phrase. No unlimited approval.
Private by default — Funding and spending are deliberately unlinked — not just a stealth address.
Still auditable — Every payment has a receipt. Export what you need for finance or compliance — nothing more.
Connect through MCP, compile a plan, enforce policy, and retain the result with proof.
How it works
Three steps from a connected agent to an inspectable commerce Mission. Prototype execution is clearly disabled.
1.0 — Connect
Connect an agent through MCP and bind it to a human-reviewed policy. The agent gets scoped commerce authority, never your treasury.



2.0 — Plan
A goal or payment intent becomes an endpoint, method, payload, maximum price, privacy route, and deterministic policy trace.
Settled.
The request was within the per-request cap and the merchant is on the allowlist, so it was authorized and settled on Elysium.
The resource was delivered only after settlement. A receipt with a hash was issued, and you can check it against the transaction. (Sample receipt.) Signatures and proofs are never stored.
3.0 — Execute & prove
Inside policy, the production runner may settle automatically. The resource, lifecycle, policy trace, and receipt stay together in one Run Artifact.
Deposits and withdrawals are still public. Timing, amounts, and network metadata can still correlate activity. We design for real privacy, not a promise we can’t keep.
Read the privacy modelGive agents a budget, an allowlist, and a receipt trail — and keep the keys to yourself.
Settled.
The request was within the per-request cap and the merchant is on the allowlist, so it was authorized and settled on Elysium.
The resource was delivered only after settlement. A receipt with a hash was issued, and you can check it against the transaction. (Sample receipt.)
From vendor access to paid resources, every payment stays inside the policy you set.
Built on Elysium · x402-compatible · non-custodial