Swap USDC for PRB (prettybitch) tokens on Base via a single x402-authenticated GET request.
What it does
This x402 endpoint at prb.x420.dev allows agents and users to purchase PRB (prettybitch, contract 0xb02ec227Ba060Ee60E205c8a626F2330DD4a5B07) tokens on the Base network by paying USDC. The endpoint uses the x402 payment protocol: callers attach an X-PAYMENT header containing a payment proof for the requested USDC amount, and the service executes a token swap on their behalf, returning the swap transaction hash and the number of PRB tokens received.
The payment challenge specifies a maximum amount of 1,000,000 units (1 USDC, given USDC's 6 decimal places) paid to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd using USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. The response includes fields for the swap transaction hash, a send transaction hash, the number of tokens received, and the USDC amount paid. According to the landing page, the service has processed 49 total transactions across 19 unique users, with an average latency of 2.68 seconds and an 89% success rate.
The endpoint is part of the x420.dev platform, which appears to host x402-enabled token purchase services for various Clanker-created tokens. No formal API documentation, OpenAPI spec, or pricing page exists beyond the x402 challenge itself and the landing page stats.
Capabilities
Use cases
- —Agents autonomously purchasing PRB tokens by paying USDC via x402
- —Programmatic token swaps on Base without managing DEX interactions directly
- —Automated portfolio building that includes meme/community tokens on Base
Fit
Best for
- —AI agents that need to acquire PRB tokens programmatically
- —Developers integrating x402 payment flows for on-chain token purchases
- —Users who want a simple HTTP-based interface to swap USDC for PRB on Base
Not for
- —Purchasing tokens on networks other than Base
- —Swapping arbitrary token pairs — this endpoint only sells PRB for USDC
- —Users needing detailed swap routing control or limit orders
Quick start
curl -X GET https://prb.x420.dev/api/puff \
-H "X-PAYMENT: <x402-payment-proof>"Example
Response
{
"message": "Successfully swapped USDC for PRB tokens",
"tokensReceived": "42000000000000000000",
"usdcAmountPaid": "1000000",
"sendTransactionHash": "0x789abc...012def",
"swapTransactionHash": "0xabc123...def456"
}Endpoint
Quality
The x402 challenge is live and provides a clear output schema, but there is no formal API documentation, no OpenAPI spec, and the /docs, /api, /pricing, and /README paths all return placeholder pages. Stats from the landing page provide some operational context but are limited. The response schema is inferred from the outputSchema in the challenge.
Warnings
- —No API documentation exists — /docs, /api, /pricing, and /README all return 'doesn't exist' pages
- —No OpenAPI or machine-readable spec available
- —Success rate reported at 89%, meaning roughly 1 in 9 transactions may fail
- —The example response JSON is fabricated from the outputSchema; no real response sample was captured
- —PRB is a meme/community token (prettybitch) — token value and liquidity are unpredictable
Citations
- —The x402 challenge requires 1,000,000 units (1 USDC) paid on Base network to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbdhttps://prb.x420.dev/api/puff
- —PRB token contract address is 0xb02ec227Ba060Ee60E205c8a626F2330DD4a5B07, created by 0xCe9e...0429https://prb.x420.dev
- —49 total transactions, 19 unique users, 2.68s average latency, 89% success ratehttps://prb.x420.dev
- —The output schema includes message, swapTransactionHash, sendTransactionHash, tokensReceived, and usdcAmountPaid fieldshttps://prb.x420.dev/api/puff
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://prb.x420.dev/api/puff