Buy custom USDC amounts of $nine token (0x3a10…1B07) via x402 payment protocol.
What it does
This x402-enabled endpoint on the x420.dev platform allows agents and users to purchase a custom USDC amount worth of the $nine token (contract 0x3a105f1247B27DED116B5d8dFe3D8e24151c1B07). The $nine token was created via Clanker and is associated with the "nine to five" project. The endpoint is hosted at nine.x420.dev and uses the x402 payment protocol to gate access behind a USDC micropayment.
According to the site's x402 stats, the endpoint has extremely low usage: 1 total transaction, 1 unique user, an average latency of 2.31 seconds, and a 100% success rate. The trust score is listed at 82%. The site provides a simple "Puff" action where users enter a USDC amount to spend. There is also a Clanker rewards claim feature for WETH.
Documentation is essentially nonexistent — the /docs, /api, /pricing, and /README paths all return placeholder pages. No OpenAPI schema, no request/response examples, and no formal pricing information are available. The probe did not return a standard 402 challenge from the endpoint (received 405 instead), which raises questions about the endpoint's current operational status.
Capabilities
Use cases
- —Programmatically purchasing $nine tokens with a specified USDC amount
- —Agent-driven token acquisition via x402 micropayments
- —Automating small token buys as part of a DeFi workflow
Fit
Best for
- —Agents or users wanting to buy $nine tokens with USDC
- —x402-compatible clients looking for token purchase endpoints
- —Experimenting with x402 payment-gated token swaps
Not for
- —Production-grade high-volume token trading
- —Users needing detailed API documentation or SLAs
- —Non-crypto or non-x402 use cases
Quick start
# The endpoint expects an x402 payment flow.
# POST to the puff-custom endpoint with a USDC amount.
curl -X POST https://nine.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-d '{"amount": "1.00"}'Example
Request
{
"amount": "1.00"
}Endpoint
Quality
No documentation, no OpenAPI schema, no response examples, and the probe returned 405 instead of a 402 challenge. Nearly all details are inferred from the sparse landing page. This is effectively a stub listing.
Warnings
- —Probe returned HTTP 405 instead of expected 402 challenge — endpoint may not be operational or may require specific HTTP methods
- —No documentation exists: /docs, /api, /pricing, /README all return placeholder pages
- —Extremely low usage (1 total transaction, 1 unique user) suggests this is experimental or barely used
- —Request and response schemas are entirely inferred — no official specification available
- —Token purchases involve financial risk; verify contract and endpoint legitimacy independently
Citations
- —$nine token contract address is 0x3a105f1247B27DED116B5d8dFe3D8e24151c1B07 and was created via Clankerhttps://nine.x420.dev
- —x402 stats show 1 total transaction, 1 unique user, 2.31s avg latency, 100% success rate, 82% trust scorehttps://nine.x420.dev
- —The /docs, /api, /pricing, and /README paths return placeholder 'doesn't exist' pageshttps://nine.x420.dev/docs
- —Probe returned HTTP 405 from the puff-custom endpoint instead of a 402 challengehttps://nine.x420.dev/api/puff-custom