Pay 1 USDC via x402 to buy x420 tokens on Base, returned to your wallet automatically.
What it does
The x420 /api/puff endpoint is an x402-enabled token purchase API hosted on x420.dev. When an agent or client sends a GET request with a valid X-PAYMENT header containing 1 USDC (on Base network), the server executes a swap and sends the resulting x420 tokens back. The response includes the swap transaction hash, send transaction hash, the number of tokens received, and the USDC amount paid.
x420.dev is a "launchpad" platform where users can deploy their own x402-ready tokens, each receiving a dedicated subdomain and x402 purchase API. Tokens are launched via Clanker with instant liquidity, and deployers earn trading fees. The x420 token itself (ticker $x420) is the platform's flagship token with a reported market cap around $178k at time of crawl.
The endpoint uses the x402 payment protocol (version 1, "exact" scheme) on the Base L2 network. The payment asset is USDC at contract 0x8335...2913, and the payment recipient is 0x9310...fdbd. The maximum timeout for payment settlement is 120 seconds. No OpenAPI spec or detailed API documentation is available — the /docs, /api, /pricing, and /README paths all return "Subdomain Not Found" errors.
Capabilities
Use cases
- —AI agents autonomously purchasing x420 tokens using USDC via the x402 payment protocol
- —Programmatic token acquisition on Base without manual wallet interaction
- —Demonstrating x402 payment flows with a real on-chain swap
Fit
Best for
- —Developers experimenting with x402 payment protocol integrations
- —Autonomous agents that need to acquire x420 tokens on Base
- —Testing x402 payment flows against a live endpoint
Not for
- —Large-volume or institutional token trading (fixed 1 USDC amount per call)
- —Users seeking tokens on networks other than Base
- —Anyone needing detailed API documentation or SLA guarantees
Quick start
curl -X GET https://x420.dev/api/puff \
-H "X-PAYMENT: <x402-payment-header-with-1-USDC-on-Base>" \
-H "Accept: application/json"Example
Response
{
"message": "Swap successful",
"tokensReceived": "42000.0",
"usdcAmountPaid": "1.0",
"sendTransactionHash": "0x789ghi...jkl012",
"swapTransactionHash": "0xabc123...def456"
}Endpoint
Quality
No OpenAPI spec, no dedicated documentation (all doc paths return 404-like pages), and no usage examples are provided. The output schema is available only from the x402 challenge header. The endpoint is live and the x402 challenge is well-formed, but critical details like token contract address, slippage handling, and error responses are undocumented.
Warnings
- —No API documentation available — /docs, /api, /pricing, /README all return 'Subdomain Not Found'
- —No OpenAPI or machine-readable schema beyond the x402 challenge outputSchema
- —Fixed 1 USDC purchase amount with no apparent configurability
- —Meme token with speculative value — token price and liquidity may be highly volatile
- —The response example is inferred from the outputSchema; no real response sample was captured
Citations
- —The x402 challenge specifies 1,000,000 units (1 USDC) on Base network with exact schemehttps://x420.dev/api/puff
- —Payment recipient is 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd and USDC asset is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://x420.dev/api/puff
- —x420 token reported market cap around $178k; platform allows deploying x402-ready tokens via Clankerhttps://x420.dev
- —The outputSchema includes message, swapTransactionHash, sendTransactionHash, tokensReceived, and usdcAmountPaid fieldshttps://x420.dev/api/puff