Buy x420 tokens with a custom USDC amount via x402 payment protocol on Base.
What it does
This x402-enabled endpoint allows agents and users to purchase x420 tokens (contract 0x68e284F21D04D4D62398C290EC3EF41C97F80b07) by spending a custom USDC amount. The x420 token was created via Clanker on the Base network. The endpoint is part of the x420.x420.dev platform, which tracks x402 transaction statistics and provides a "Puff" action where users specify a USDC amount to swap for x420 tokens.
Based on the site's x402 stats, the service has processed 10 total transactions from 6 unique users with a 100% success rate and an average latency of 2.29 seconds. The trust score is listed at 85%. The endpoint returned HTTP 405 (Method Not Allowed) on a probe GET request rather than the expected 402 challenge, which suggests it may require a POST method or specific parameters to trigger the x402 payment flow.
Documentation is essentially nonexistent — the /docs, /api, /pricing, and /README paths all return placeholder pages. No OpenAPI schema, pricing details, or formal API documentation were found. The token is viewable on Clanker and x402scan for on-chain verification.
Capabilities
Use cases
- —Programmatically purchasing x420 tokens with USDC via an AI agent
- —Automating token acquisition as part of a DeFi workflow
- —Integrating x402-based micropayments for token swaps into agent pipelines
Fit
Best for
- —Agents that need to autonomously acquire x420 tokens on Base
- —Developers experimenting with x402 payment protocol for token purchases
- —Users wanting a simple USDC-to-x420 swap interface
Not for
- —Users seeking detailed API documentation or OpenAPI specs
- —Production systems requiring well-documented, stable APIs
- —Non-crypto or non-DeFi use cases
Quick start
# The endpoint expects an x402 payment flow.
# Trigger a purchase by POSTing to the puff-custom endpoint:
curl -X POST https://x420.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-d '{"amount": "1.00"}'Example
Request
{
"amount": "1.00"
}Endpoint
Quality
No OpenAPI schema, no documentation pages (all return placeholder), no x402 challenge returned on probe (405 instead of 402), and no example responses available. The listing is largely inferred from the homepage stats and the existing title/description. This is effectively a stub.
Warnings
- —Endpoint returned HTTP 405 instead of expected 402 challenge — x402 flow may require POST or specific headers
- —No API documentation exists; /docs, /api, /pricing, /README all return placeholder pages
- —Request and response schemas are entirely inferred — no formal spec available
- —Token purchase involves financial transactions; verify on-chain contract before use
- —Very low transaction volume (10 total) suggests early-stage or experimental service
Citations
- —x420 token contract address is 0x68e284F21D04D4D62398C290EC3EF41C97F80b07https://x420.x420.dev
- —10 total transactions from 6 unique users with 100% success rate and 2.29s average latencyhttps://x420.x420.dev
- —Trust score is 85%https://x420.x420.dev
- —Token was created via Clanker and is viewable on clanker.worldhttps://x420.x420.dev
- —Endpoint returned HTTP 405 on probehttps://x420.x420.dev/api/puff-custom