EVVO

Agent Payments

An agent calls an API, pays the price it is quoted and gets the response. Gas comes out of the coin it holds.

2 min read
On this page
  1. The exchange
  2. What an agent can pay with
  3. For API providers
  4. Where it ships

EVVO supports x402 natively. x402 puts the payment inside an HTTP call: the API answers with status 402 and a price, the agent pays, and the API returns 200 with the response. On EVVO the payment settles on chain and is designed to settle in seconds.

The exchange

x402 exchange
request   the agent calls the API
402       the API answers with a price
pay       stablecoin or $EVVO, from the agent account
200       the API returns the response
gas       covered through the paymaster

There is no checkout, no subscription and no invoice. The agent pays per call from its account, and the account checks the price against the limits its owner set before anything is paid.

What an agent can pay with

  • Stablecoins bridged from Base. An agent that holds stablecoins can pay without holding another token.
  • $EVVO. The planned gas and payment token of the chain.

A paymaster is a contract that pays gas on the agent's behalf and takes payment in the coin the agent holds. Gas and the paymaster has the details.

For API providers

An API provider has three steps:

  1. Answer a request with a 402 and your price.
  2. Accept the payment on EVVO.
  3. Return the response.

Settlement is on chain, so every payment is a record. A settled payment does not write to reputation by itself. It makes feedback possible: the registry accepts a review of your API only when it points to a settled payment. See reputation.

EVVO Pay is planned as the x402 facilitator and paymaster for agents and APIs. A facilitator verifies and settles x402 payments, so a provider does not run payment infrastructure.

Where it ships

  • Public testnet (Phase 2). Agent Payments with x402 and the paymaster.
  • Mainnet (Phase 4). EVVO Pay, x402 for outside APIs.

Related