Agent commerce, without treasury keys

Connect an agent. Give it a goal or x402 payment intent. Elypx402 builds the plan, enforces policy, and retains the result with proof.

Launch app
Elysium
x402
USDC
HYPE
Security model

Built on Elysium · x402-compatible · non-custodial

Elypx402 is an Agent Commerce OS
built to turn bounded goals into provable purchases

very402 / elysium · chain 99901
E4
Private account
Z60%
Elypx402
Policy
Agents
Vendors
Payments
Audit
Policies
Receipts
Resources
Mission ControlAgent AccountsMissionsNetworkDeveloper
Ask Elypx402 to compile a commerce Mission...

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.

Give your agent a commerce mission.

Connect through MCP, compile a plan, enforce policy, and retain the result with proof.

Launch app

How it works

Connect an agent. Define the boundary. Let Elypx402 compile the purchase.

Three steps from a connected agent to an inspectable commerce Mission. Prototype execution is clearly disabled.

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 stage1/1
Plan stage0/3
Execute stage0/4
Connect walletYou do this
Create private accountYou do this
Deposit USDCAutomatic
ScreeningNeeds your signature
Set budget capsAutomatic
Pick merchantsYou do this
Review policyAutomatic
Sign policyNeeds your signature

2.0 — Plan

Compile a goal into a Payment Plan

A goal or payment intent becomes an endpoint, method, payload, maximum price, privacy route, and deterministic policy trace.

Payment Receipt
Merchant
Data vendordata.vendor.example
Agent
Payment agentpolicy v1 · data-agent
ResourceGET /v1/data · 0.02 USDC

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.

Policy Report
Daily cap used
4%
12%
Settled3
Remaining6
Merchants-
Requests0
Allowed0
Blocked
0%
0
Receipts
0%
0

3.0 — Execute & prove

Deliver the resource, retain the proof

Inside policy, the production runner may settle automatically. The resource, lifecycle, policy trace, and receipt stay together in one Run Artifact.

Settled
115
+12%
Requests
128
+9%
Blocked
13
+3%
Spend over time
400k300k200k100k
0 ns
0.50 s
1.00 s
1.50 s
2.00 s
2.50 s
3.00 s
3.50 s
4.00 s
Vendors
Payments
Receipts
Latest receipts
2,843 receipts issued this week

Private, not untraceable

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 model

All the controls your agents need

Give agents a budget, an allowlist, and a receipt trail — and keep the keys to yourself.

Payment Receipt
MerchantData vendordata.vendor.example
AgentPayment agentpolicy v1 · data-agent
ResourceGET /v1/data · 0.02 USDC

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.)

Payment receipt
1/3

Spend across every workflow

From vendor access to paid resources, every payment stays inside the policy you set.

Z
S
M
D
H
L
A
E
J
U
U
R
G
T
P
S
B
V
E
T
O
D
U
R
N
L
L
C
D
E
T
E
I
I
G
C
P
M
C
Q
E
E
E
E
Y
M
T
I
B
N
F
J
P
P
G
T
O
Y
E
T