Frequently asked questions

Choose a package on the checkout page, select a supported network and USDC or USDT, then follow the payment instructions. A successful payment produces a one-time access token. Keep it private and do not put it in a URL or browser storage.

Use the token as the SOCKS5 username and password, or follow the agent instructions in llms.txt. The Usage dialog can show status, expiry, traffic, and active exits without retaining the token.

Chrome cannot ask for SOCKS5 credentials itself (the SOCKS5 username/password prompt is delegated to the operating system, which has no such prompt), so a plain SOCKS5 token cannot be typed into Chrome's proxy settings. Two ways to connect directly: (1) HTTP CONNECT (live on us-central1, eu-central1, and asia-central2) - point Chrome at --proxy-server=http://us-central1.x402socks.com:3128 (or set it in system proxy settings); use eu-central1.x402socks.com:3128 or asia-central2.x402socks.com:3128 for the other selected exits. On the first request Chrome shows its built-in credential dialog after HTTP 407 - enter your token as both the username and the password. PAC files and manual proxy settings work the same way. The HTTP variant is plaintext (like any unencrypted proxy hop). HTTPS CONNECT (the same HTTP proxy over TLS) is available on asia-central2 only, on port 3129 - use https://asia-central2.x402socks.com:3129 in curl or Firefox, or a PAC entry HTTPS asia-central2.x402socks.com:3129; address it by hostname, not IP, because the certificate is issued for that name. The other four exits are SOCKS5-only. (2) SOCKS5 on port 1080 is always available on every exit - use a proxy-management extension or a local forwarder that supplies the token as the SOCKS5 username and password, or use any other SOCKS5-capable client. Either dialect uses the same token, the same entitlements, and the same accounting. Agent details are in llms.txt.

The checkout displays the currently enabled API-authoritative rails. Select the network first, then choose one of the stablecoins offered for that network. Do not send funds on another chain or use a different token or amount.

Time packages expire at their displayed entitlement time. Usage packages end when their byte allowance is exhausted. The service can close active sessions when an entitlement expires or is exhausted; check the Usage dialog for the current state.

First confirm the selected network, token, and exact amount, then wait for the checkout status to update. Do not pay a second time for the same intent. If the payment is confirmed but access is not issued, keep the payment reference and ask in the Telegram channel.

If an x402 payment settled and you still control the paying wallet, you can recover the credentials without paying again: sign the recovery message from that wallet and POST it to https://payments.x402socks.com/v1/access/recover, as documented in llms.txt. Recovery re-issues the token only while the paid plan is active. If the plan has expired, or the payment is not confirmed yet, do not pay a second time - keep the transaction hash and ask in the Telegram channel.

If you still hold your token, send POST https://api.x402socks.com/api/v1/token/rotate with the current token as the Bearer authorization header; the response contains a new token and the old one stops working immediately, so update every client you control right away. The exact request is documented in llms.txt. A token you no longer have cannot be rotated - use the recovery answer above.