Buy ROLLAK tokens with a custom USDC amount via x402 payment on Base.
What it does
This x402-enabled endpoint allows callers to purchase ROLLAK tokens (contract 0x287f28Ea9740D09cdff1ddd1faC4209fc40BdB07) by specifying a custom USDC amount. The token is hosted on the x420.dev platform, which wraps Clanker-launched tokens with x402 payment gates. The front-end refers to the purchase action as a "Puff," where users enter a USDC amount and execute the swap.
The ROLLAK token was created via Clanker (a token launcher on Base) and is associated with the creator address 0xb547...b23e. The endpoint is served at rollak.x420.dev and is linked to x402scan for on-chain activity tracking. Clanker reward claiming (WETH) is also available through the front-end but appears to be a separate wallet-connected flow.
Documentation is essentially nonexistent — the /docs, /api, /pricing, and /README paths all return placeholder pages. The probe did not return a 402 challenge (received 405 instead), and no OpenAPI schema, agents.txt, or ai-plugin manifest was found. As a result, the exact request format, accepted parameters, pricing structure, and response schema are unknown and must be treated as unverified.
Capabilities
Use cases
- —Programmatically purchasing ROLLAK tokens with USDC via an x402 payment flow
- —Agent-driven token acquisition on Base without manual wallet interaction
- —Integrating meme-token purchases into automated trading or tipping workflows
Fit
Best for
- —Agents or bots that need to buy specific Clanker-launched tokens on Base
- —x402-native payment flows where USDC is the settlement currency
- —Automated micro-purchases of community/meme tokens
Not for
- —Users needing detailed API documentation or guaranteed uptime SLAs
- —Production trading systems requiring well-documented schemas and error handling
- —Non-Base-chain token purchases
Quick start
# No verified request schema available. Based on the UI, the endpoint likely accepts a USDC amount.
# Example (speculative — verify before use):
curl -X POST https://rollak.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-d '{"amount": "1.00"}'Endpoint
Quality
No API documentation, no OpenAPI schema, no x402 challenge returned (405 instead of 402), and all doc/pricing/readme paths are placeholder pages. The listing is effectively a stub with only the front-end landing page providing minimal context.
Warnings
- —Endpoint returned HTTP 405 instead of the expected 402 challenge during probing — may not be functioning as a standard x402 endpoint.
- —No documentation exists: /docs, /api, /pricing, and /README all return 'doesn't exist' placeholders.
- —No OpenAPI schema, agents.txt, or ai-plugin manifest found.
- —Request and response formats are entirely unknown; the quick_start_snippet is speculative.
- —This involves purchasing a meme/community token — exercise caution regarding financial risk and regulatory considerations.
Citations
- —ROLLAK token contract address is 0x287f28Ea9740D09cdff1ddd1faC4209fc40BdB07, created by 0xb547...b23ehttps://rollak.x420.dev
- —Token was launched via Clanker and is viewable on clanker.worldhttps://rollak.x420.dev
- —On-chain activity is tracked via x402scan at the listed recipient addresshttps://rollak.x420.dev
- —The /docs, /api, /pricing, /README paths return placeholder 'doesn't exist' pageshttps://rollak.x420.dev/docs
- —Probe returned HTTP 405 instead of 402 challengehttps://rollak.x420.dev/api/puff-custom