FAQ
Updated:
The questions that come up most often when an agent works with the x402 API.
Payments
A regular Ethereum wallet (with a private key) that holds USDC on Base. You do not need ETH: the transfer is submitted to the network for you.
Catalog prices are for one unit at the minimum quantity and are for reference. The 402 price is calculated for your exact order, with volume discounts. Only the 402 price is binding.
No. Send the same request with the same PAYMENT-SIGNATURE: you get the result of the first attempt. Sign a new authorization only when the API tells you so (retry_action: resign) or after authorization_expires_at.
A quote can be paid only once. If another payment for it comes first, your payment is rejected before any funds are taken, and the response tells you what to do: wait, or sign the new quote that comes with it.
No. A payment is checked against the signature of the wallet; a forged address fails the check before any funds move, and does not use up your limits.
Orders
No. Each payment is confirmed on the Base network before the order is fulfilled. This usually takes a few minutes. Keep polling.
The proxies are being issued later than usual. Keep polling: the order becomes active once they are issued. Mobile proxies are issued manually by our staff and may take up to 3 hours.
The proxies could not be issued automatically. The payment is safe: our staff issue the proxies manually, and the order becomes active by itself. If it is urgent, write to [email protected] with the order id.
Our staff are checking the operation. Do not pay again; write to support with the order id if you need an answer quickly.
In lines[].proxies[] of Get order. For residential traffic — in resident.connection.
Use any ip from gateways of the proxy with its port_http or port_socks5 and its own login and password. If one gateway does not respond, switch to another.
Residential
With suffixes in the login: _c_US for a country, _city_<City-Name> for a city, _s_<session_id> for a sticky session, _ttl_30m for its lifetime. Without suffixes every request gets a new IP. The full syntax is in resident.connection.targeting.
A wallet has one package. Add traffic to it with Add traffic; this also restarts its period.
It expires with the package.
Access
Use Recover access: sign a message with the paying wallet and get new tokens for all its orders.
Recover access with revoke_existing: true: all earlier tokens of the wallet are revoked.
Without a link to an account, orders bought through x402 are managed only through the x402 API, with the access token of the order. Once the owner of an account links the wallet to it, the orders paid after that belong to the account: the owner manages them in the dashboard too, while the agent keeps using the x402 API with the access token of the order (Link to an account).
Yes, once the owner of the account links the wallet of the agent to it: the orders paid after that appear in the dashboard and the top-ups of the wallet go to the balance of the account (Link to an account).
Refunds and withdrawals
The unused balance can be withdrawn to the paying wallet (Withdraw balance). Payments for orders are not refunded through the API; contact support with the order id.
New payments get 403 wallet_rejected, recovery lists your orders without tokens, and withdrawals are rejected. Contact support.