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 and HYPE · more chains coming soon · 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.

An AI agent often needs to pay for data or an API. Elypx402 sits in between: you set the spending limits once, the agent asks before it buys, and every request is checked against your rules and kept as a record. The agent never holds your main wallet.

  1. 01

    Connect an agent

    Install the Elypx402 MCP server in the agent you already use. It gets a token scoped to one Agent Account, never your main wallet.

    Seed phrases and main-wallet keys are never requested.
  2. 02

    Define the boundary

    Pick which vendors the agent may pay, which HTTP methods it may use, and the per-request, daily and lifetime caps in USDC.

    The same rules are checked again at execution, not just at planning.
  3. 03

    Compile and inspect

    The agent describes what it needs. Elypx402 returns an ALLOW or BLOCK with each check and a suggested policy change, and keeps the Mission.

    Today this ends at the decision. Payment execution is switched off until a verified Elysium runner is live.
Your agentClaude Code, Codex, Cursor and more
Elypx402policy · plan · audit
x402 vendorpays only if allowed

Install the MCP server

Add it to your agent in one command.

Package @elypx402/mcp · Node 20+ · 9 tools · 8 clients

Run in your terminal

claude mcp add elypx402 --transport stdio \
  --env ELYPX402_BASE_URL=https://api.elypx402.com \
  --env ELYPX402_TOKEN=<scoped-token> \
  -- npx -y @elypx402/mcp

Then run /mcp inside Claude Code to confirm elypx402 is connected.

What your agent can call

  • elypx402_statusreadiness and honest execution state
  • list_agent_accountsaccounts visible to the token
  • preview_payment_planpolicy decision, nothing saved
  • create_payment_missionsave a Mission with its trace
  • get_missionread a Mission and its checks
  • get_receiptsettlement receipt, once one exists
  • get_resourcedelivered resource, hash-matched
  • cancel_missioncancel before execution
  • execute_payment_missiondisabled until a verified runner is live

Tokens are scoped to a single Agent Account and issued by the Core API after wallet sign-in. Payment execution stays disabled until a verified Elysium runner is live. Logos identify compatible clients and do not imply endorsement.

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