Buy PEPE tokens with a custom USDC amount via x402 payment on Base
What it does
This x402-enabled endpoint at pepe.x420.dev allows agents and users to purchase PEPE tokens (contract 0x2CBCb4a8Db7Ebe8E9Be3329A75252E53D0993b07) by spending a custom amount of USDC. The token was created via Clanker and is hosted on the x420.dev platform, which wraps token purchases behind x402 paywalled endpoints.
The landing page exposes a "Puff" action where the caller specifies a USDC amount to spend. On-chain x402 stats show very low usage: 1 total transaction, 1 unique user, an average latency of 2.34 seconds, and a 100% success rate. The trust score listed is 82%. The endpoint is supposed to return a 402 challenge for x402 negotiation, but during probing it returned HTTP 405, suggesting the endpoint may only accept POST requests or may have intermittent availability issues.
Documentation is essentially absent — the /docs, /api, /pricing, and /README paths all return a placeholder page stating the subdomain doesn't exist, despite the root page rendering correctly. No OpenAPI spec, agents.txt, or ai-plugin manifest was found. Because of the lack of schema documentation and the 405 probe response, integration details must be inferred entirely from the landing page UI.
Capabilities
Use cases
- —Programmatically purchasing PEPE tokens with USDC via an x402-authenticated API call
- —Integrating meme-token purchases into an autonomous agent's workflow on Base
- —Automating small USDC-denominated token swaps without a DEX frontend
Fit
Best for
- —Agents that need to acquire specific ERC-20 tokens on Base via x402
- —Developers experimenting with x402 payment protocol for token swaps
- —Automated trading bots targeting Clanker-launched tokens
Not for
- —Production trading requiring reliable uptime and documented API schemas
- —Large-volume or low-latency trading where a direct DEX integration is preferable
- —Users seeking tokens on chains other than Base
Quick start
# The endpoint expects an x402 payment flow. A minimal curl attempt:
curl -X POST https://pepe.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-d '{"amount": "1.00"}'Example
Request
{
"amount": "1.00"
}Endpoint
Quality
No OpenAPI spec, no documentation pages (all return placeholder), no agents.txt, probe returned 405 instead of 402, and the only information available is from the landing page UI. Almost everything about the request/response schema is inferred. Effectively a stub listing.
Warnings
- —Probe returned HTTP 405 instead of the expected 402 challenge — endpoint may be POST-only or intermittently unavailable
- —All documentation paths (/docs, /api, /pricing, /README) return a 'doesn't exist' placeholder
- —No OpenAPI schema, ai-plugin manifest, or agents.txt found
- —Extremely low usage: only 1 total transaction and 1 unique user reported
- —Request and response schemas are entirely inferred from UI labels; no authoritative spec exists
- —This involves purchasing a meme token — high financial risk and potential for loss
Citations
- —PEPE token contract address is 0x2CBCb4a8Db7Ebe8E9Be3329A75252E53D0993b07, created via Clankerhttps://pepe.x420.dev
- —x402 stats: 1 total transaction, 1 unique user, 2.34s avg latency, 100% success rate, 82% trust scorehttps://pepe.x420.dev
- —The Puff action accepts a custom USDC amounthttps://pepe.x420.dev
- —Probe returned HTTP 405 instead of 402https://pepe.x420.dev/api/puff-custom
- —Documentation paths return placeholder 'doesn't exist' pageshttps://pepe.x420.dev/docs