Start without registration
No registration, account, API key, or prepaid balance is required. Discover the live contract at GET /v1/x402, then use the x402 API documentation for complete request and response schemas.
- Read
GET /v1/x402for current endpoints and supported payment networks. - Create a rate-locked rental quote with
POST /v1/x402/quotes. - POST the returned payment URL once to receive the x402 challenge.
- Pay one option, retry with
PAYMENT-SIGNATURE, then poll the returned status URL.
Accepted x402 payments
| Priority | Asset | Network | Use |
|---|---|---|---|
| Preferred | USDC | Base | First choice for compatible agents |
| Fallback | USDC | Solana | Use when the agent is funded on Solana |
The 402 Payment Required response is the source of truth for network identifiers, token addresses, recipients, expiry, and the exact atomic payment amount.
Standard x402 payment flow
The first payment request returns 402 with PAYMENT-REQUIRED. Select Base USDC when available or Solana USDC as the fallback, sign through the agent's wallet, and retry the same URL with PAYMENT-SIGNATURE. A successful settlement returns PAYMENT-RESPONSE.
The quote fixes the Energy amount, rental duration, target TRON address, USDC amount, and expiry before payment. The status endpoint reports both payment settlement and Energy delivery.
Machine-readable rates and rental status
Use the x402 capability endpoint for discovery and Swagger's x402 section for field-level schemas. Bots should use those API responses instead of scraping this page for prices or payment details.
