Swap USDC for DREAM tokens on Base via a pay-per-call x402 endpoint
What it does
This x402 endpoint at dream.x420.dev allows callers to purchase DREAM tokens (contract 0xD7dA53A5d367CB31447FF74E3F9EEBd0e6932b07) by paying 1 USDC per call on the Base network. The endpoint uses the x402 exact payment scheme: an agent sends a GET request with an X-PAYMENT header containing a valid payment proof, and the service executes a token swap on the caller's behalf, returning the swap transaction hash, send transaction hash, the number of tokens received, and the USDC amount paid.
The DREAM token was created via Clanker and is associated with the "Fresh Funded" project. According to the landing page, the service has processed a small number of transactions (4 total at time of crawl) with a 100% success rate and an average latency of about 2.6 seconds. The trust score reported by x402scan is 81%. Payment is made to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd in USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base.
No formal API documentation, OpenAPI spec, or additional endpoints are available beyond the single /api/puff resource. The output schema provided in the x402 challenge describes the response shape, but there is no further developer documentation.
Capabilities
Use cases
- —Programmatically purchasing DREAM tokens with USDC via an AI agent
- —Automating small token swaps on Base without a DEX frontend
- —Integrating token purchases into agent workflows using x402 payment protocol
Fit
Best for
- —AI agents that need to acquire DREAM tokens autonomously
- —Developers experimenting with x402 pay-per-call token swaps
- —Automated trading or portfolio bots on Base
Not for
- —Large-volume or high-frequency token trading (single fixed-amount endpoint)
- —Purchasing tokens other than DREAM
- —Users who need detailed API documentation or SLA guarantees
Quick start
# GET with x402 payment header (1 USDC on Base)
curl -X GET https://dream.x420.dev/api/puff \
-H "X-PAYMENT: <x402_payment_proof>"Example
Response
{
"message": "Successfully swapped USDC for DREAM tokens",
"tokensReceived": "42000.0",
"usdcAmountPaid": "1.0",
"sendTransactionHash": "0x789abc...012def",
"swapTransactionHash": "0xabc123...def456"
}Endpoint
Quality
The x402 challenge is live and provides a clear output schema and payment details, but there is no API documentation, no OpenAPI spec, and the docs/pricing/README pages all return placeholder 'doesn't exist' pages. Transaction volume is very low (4 total). The response example is inferred from the outputSchema rather than observed.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README all return placeholder pages
- —Very low transaction volume (4 total transactions at time of crawl)
- —Response example is inferred from outputSchema, not from an actual observed response
- —Single fixed-amount endpoint (1 USDC) with no configurable parameters documented
- —DREAM token is a Clanker-created token — do your own research on token legitimacy and liquidity
Citations
- —The endpoint returns a 402 challenge requiring 1,000,000 units (1 USDC) payment on Basehttps://dream.x420.dev/api/puff
- —DREAM token contract is 0xD7dA53A5d367CB31447FF74E3F9EEBd0e6932b07https://dream.x420.dev
- —4 total transactions, 100% success rate, 2.61s average latency, 81% trust scorehttps://dream.x420.dev
- —Token was created via Clanker by 0xfE7f...5b69https://dream.x420.dev
- —Payment recipient is 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd using USDC asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://dream.x420.dev/api/puff