Buy a custom USDC amount of MUNCH tokens via x402 payment protocol
What it does
This x402-enabled endpoint at munch.x420.dev allows callers to purchase MUNCH tokens (contract 0x70B1dC3d736F164befCb23388608DD822b253B07) by spending a custom amount of USDC. MUNCH is a token created via Clanker on Base, and the endpoint is part of the x420.dev platform which hosts x402-compatible token purchase actions.
Based on the landing page stats, the endpoint has processed 36 total transactions from 14 unique users with an average latency of 2.68 seconds, an 86% success rate, and a trust score of 80%. The UI labels the action as "Puff" and accepts an amount in USDC as input. No formal API documentation, OpenAPI schema, or pricing details are available — the /docs, /api, /pricing, and /README paths all return placeholder pages. The probe also did not receive a standard 402 challenge from the endpoint (returned 405 instead), which may indicate the endpoint requires a specific HTTP method or additional headers.
Given the lack of documentation and schema, integrating this endpoint requires experimentation or reverse-engineering the request format. The token can be verified on Clanker and activity can be tracked on x402scan.
Capabilities
Use cases
- —Programmatically purchasing MUNCH tokens with USDC via an AI agent
- —Automating token buys through x402 payment flows
- —Integrating meme-token purchases into agent workflows
Fit
Best for
- —AI agents that need to buy tokens via x402 protocol
- —Developers experimenting with x402-based DeFi actions
- —Automated trading bots targeting Clanker-launched tokens
Not for
- —Users needing well-documented, production-grade swap APIs
- —High-frequency trading requiring sub-second latency
- —Purchasing tokens other than MUNCH
Quick start
# No formal schema available. Based on the UI, the endpoint likely accepts a POST with a USDC amount.
curl -X POST https://munch.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-d '{"amount": "5.00"}'Example
Request
{
"amount": "5.00"
}Endpoint
Quality
No API documentation, no OpenAPI schema, no x402 challenge returned from the probe (405 instead of 402), and all doc/api/pricing paths are placeholder pages. The request format and response structure are entirely inferred from the UI. This is effectively a stub listing.
Warnings
- —Endpoint returned 405 instead of expected 402 challenge — may require specific HTTP method or headers
- —No API documentation exists; /docs, /api, /pricing, /README all return 'doesn't exist' pages
- —Request and response schemas are entirely inferred and unverified
- —86% success rate and 80% trust score suggest some reliability concerns
- —Only 36 total transactions from 14 users — very low usage
Citations
- —MUNCH token contract is 0x70B1dC3d736F164befCb23388608DD822b253B07, created via Clankerhttps://munch.x420.dev
- —36 total transactions, 14 unique users, 2.68s avg latency, 86% success rate, 80% trust scorehttps://munch.x420.dev
- —Endpoint probe returned 405 instead of 402 challengehttps://munch.x420.dev/api/puff-custom
- —Token activity viewable on x402scanhttps://www.x402scan.com/recipient/0x93109d14f6665a9c9675290d3cd5a6c07bbafdbd/resources