Proxy-seller

Overview

Updated:

The x402 API lets AI agents and scripts buy and manage Proxy-seller proxies without an account or an API key. Every paid request is settled in USDC on the Base network with the open x402 payment protocol (version 2): the wallet that pays is the buyer.

The x402 API is a separate product from the Proxy-seller API. Orders bought here are managed only through the x402 API, with the access token of the order.

If you have not found the answer to your question, please contact us directly: [email protected]

How it works

  1. Request a price

    Send the order without payment and get 402 Payment Required with the exact amount, the recipient address and a quote valid for 15 minutes.

  2. Pay

    Sign an EIP-3009 USDC transfer authorization with your wallet and repeat the same request with the PAYMENT-SIGNATURE header. You get 202 Accepted, the order id and an access token.

  3. Get the proxies

    Poll the order with the access token. When the payment is confirmed on the network and the proxies are issued, the order becomes active and contains the connection details.

    You never send a transaction yourself: the signed authorization is submitted to the network for you, and no ETH is needed for gas. Funds are taken once and only for the exact amount of the quote.

Get started

Requirements

  • A wallet with USDC on Base. The address that signs the payment owns the order.

  • An x402 client. Any HTTP client that supports x402 version 2 with the exact scheme and EIP-3009, or your own signing code (see Payment headers).

  • The current terms. Each order confirms the versions of the terms of service and the privacy policy published in the catalog.

Base URL

https://proxy-seller.com/api/x402/v1

Network and asset

Network

Asset

Decimals

Base (eip155:8453)

USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

6

Always take the network, asset, amount and recipient from the 402 response rather than from this page.

Machine-readable descriptions

  • GET /catalog — products, countries, periods, prices, terms and protocol parameters (Catalog).

  • GET /openapi.json — OpenAPI 3.1 contract of the whole API, generated by the service itself.

Jump right in

On this page