Private spending for AI agents

Fund once. Set the budget. Let your agents pay for APIs, data, and inference on Elysium — without broadcasting what they buy or from who.

Launch app
Elysium
x402
USDC
HyperEVM
Case Studies

Built on Elysium · x402-compatible · non-custodial

Very402 is a spending control plane
built to keep every agent inside its budget

very402 / elysium · chain 99901
V4
Private account
Z60%
Very402
Research
Data
Inference
Search
Compute
Storage
Analytics
Tools
OverviewAgentsVaultActivityReceipts
Ask Very402 to set a policy for a new agent...

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.

Put your agents on a budget.

Fund once, set a policy, and let one agent make its first receipted payment.

Launch app

How it works

Fund once. Set the budget. Let your agents pay.

Three steps from a connected wallet to a receipted payment. Interface shown with sample data.

1.0 — Fund

Fund a private balance once

Deposit USDC from your operating wallet. It moves into a shielded balance that is no longer linked to it. Deposits and withdrawals stay public on-chain.

Connect stage1/1
Fund stage0/3
Policy 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 — Set policy

Give each agent a budget, not a wallet

Every agent is a scoped session key bound to caps, an expiry, and an allowlist. It can never exceed what you approved, and revoking it is final.

Payment Receipt
Merchant
Research APIapi.research.example
Agent
Research agentpolicy v1 · research-agent
ResourceGET /v1/papers · 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 — Pay

Your agents pay within policy, and every payment has a receipt

When an agent hits a paid endpoint, it gets an HTTP 402 and pays from its policy. Allowed payments settle; anything else is blocked, and you can see why.

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
Research
Data
Inference
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
MerchantResearch APIapi.research.example
AgentResearch agentpolicy v1 · research-agent
ResourceGET /v1/papers · 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 research agents to trading desks and data pipelines, 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