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
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.
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.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.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.Install the MCP server
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/mcpThen run /mcp inside Claude Code to confirm elypx402 is connected.
Run in your terminal
codex mcp add elypx402 \
--env ELYPX402_BASE_URL=https://api.elypx402.com \
--env ELYPX402_TOKEN=<scoped-token> \
-- npx -y @elypx402/mcpThis writes ~/.codex/config.toml. Check it with codex mcp list.
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project)
{
"mcpServers": {
"elypx402": {
"command": "npx",
"args": ["-y", "@elypx402/mcp"],
"env": {
"ELYPX402_BASE_URL": "https://api.elypx402.com",
"ELYPX402_TOKEN": "<scoped-token>"
}
}
}
}Restart Cursor, then enable the server under Settings → MCP.
Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"elypx402": {
"command": "npx",
"args": ["-y", "@elypx402/mcp"],
"env": {
"ELYPX402_BASE_URL": "https://api.elypx402.com",
"ELYPX402_TOKEN": "<scoped-token>"
}
}
}
}Refresh the MCP list in Cascade after saving.
Add to ~/.gemini/settings.json
{
"mcpServers": {
"elypx402": {
"command": "npx",
"args": ["-y", "@elypx402/mcp"],
"env": {
"ELYPX402_BASE_URL": "https://api.elypx402.com",
"ELYPX402_TOKEN": "<scoped-token>"
}
}
}
}Run /mcp in Gemini CLI to list connected servers.
Add to .vscode/mcp.json
{
"servers": {
"elypx402": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@elypx402/mcp"],
"env": {
"ELYPX402_BASE_URL": "https://api.elypx402.com",
"ELYPX402_TOKEN": "<scoped-token>"
}
}
}
}VS Code uses servers, not mcpServers. Start it from the MCP view.
Add to Zed settings.json
{
"context_servers": {
"elypx402": {
"command": "npx",
"args": ["-y", "@elypx402/mcp"],
"env": {
"ELYPX402_BASE_URL": "https://api.elypx402.com",
"ELYPX402_TOKEN": "<scoped-token>"
}
}
}
}Zed calls MCP servers context_servers. Check the Agent panel for a green dot.
Add to ~/.config/opencode/opencode.json
{
"mcp": {
"elypx402": {
"type": "local",
"command": ["npx", "-y", "@elypx402/mcp"],
"environment": {
"ELYPX402_BASE_URL": "https://api.elypx402.com",
"ELYPX402_TOKEN": "<scoped-token>"
},
"enabled": true
}
}
}OpenCode puts the command in one array and calls env environment.
What your agent can call
elypx402_statusreadiness and honest execution statelist_agent_accountsaccounts visible to the tokenpreview_payment_planpolicy decision, nothing savedcreate_payment_missionsave a Mission with its traceget_missionread a Mission and its checksget_receiptsettlement receipt, once one existsget_resourcedelivered resource, hash-matchedcancel_missioncancel before executionexecute_payment_missiondisabled until a verified runner is liveTokens 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.
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 and HYPE · more chains coming soon · non-custodial