Get paid by agents without publishing your customers
Agents pay per call over x402. Your price and volume stay yours.
Where Curvy sits in x402
Standard x402 between agent and service. Curvy only changes where the money lands.
Request
402 + payment terms
Signed EIP-3009 authorization
Settle
Settled to a fresh address
200 + response
What a competitor can chart today
paid calls per hour
Nothing to chart
The payments aren’t linkable to you.
Your demand curve, from public transfers. Values are illustrative.
What a public x402 address leaks
All of it is readable from one public address, by anyone, for as long as the chain exists.
- Your price One transfer gives away the rate.
- Your volume Calls per hour, counted live.
- Your customers Which agents depend on you.
- Your revenue A sum any rival can run.
How it works with x402
-
01
Agent calls
You reply 402 with terms
-
02
Agent authorizes
Standard EIP-3009 signature
-
03
Curvy settles
Fresh address, one-off or batched
-
04
You serve
Confirmed by reference
- Standard x402
- One-off or batched
- Payments SDK
- Docs for coding agents
One-off or batched?
- Cost per payment
-
Higher
- Time to settle
-
Faster
Best when something downstream waits on each confirmation.
Who sees what
This protects your side. The agent’s transfer stays public.
| who | Agent’s payment | That it paid you | Your revenue |
|---|---|---|---|
| The public | Can see | Hidden | Hidden |
| You | Can see | Can see | Can see |
| The agent’s owner | Can see | Can see | Hidden |
Before you integrate
-
Agent changes
None. Same 402 responses, same signatures.
-
Settlement cost
Batch high-volume calls to lower it.
-
Your records
Every payment, through your viewing key.
-
Custody
You hold the keys. Curvy can’t move funds.
-
What stays public
The agent’s transfer and its amount.
-
Tokens
Settles on Arbitrum. Tokens are listed in the docs.
Is it right for you?
Good fit if
- You sell API calls, data or compute to agents
- You price per call over x402
- Your customer list is commercially sensitive
- You’re happy to receive stablecoins
Not yet if
- You need fiat payouts
- You need chains other than Arbitrum
- Your agents pay on card rails
- You need the paying agent’s side private too
Built to be checked
Private, not unaccountable. How the compliance model works
Questions
Do agents need to change anything?
No. They sign the same EIP-3009 authorizations and read the same 402 responses. Only where the payment lands changes.
One-off or batched?
Batching lowers the cost per payment and adds settlement time. One-off is quicker per payment.
Can I see which agents pay me?
Yes, through your viewing key. Nobody else can.
Which tokens are supported?
Curvy Payments settles on Arbitrum. Check the docs for the tokens the x402 facilitator accepts today.