Buy x105 tokens with a custom USDC amount via x402 payment on Base
What it does
This x402 endpoint allows callers to purchase x105 tokens (contract 0x51793E001bc1f58E5da3680bD1102EEE0b713B07) by spending a custom amount of USDC on the Base network. The endpoint accepts a POST request with an optional `amount` field specifying the USDC value to spend (e.g., '10', '0.5'); if omitted, it defaults to 5 USDC. The maximum payment accepted per call is 5 USDC (maxAmountRequired: 5000000 in 6-decimal USDC units). Payment is made via the x402 protocol using USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base.
On success, the endpoint returns a JSON object containing a message, the swap transaction hash, the send transaction hash, the number of tokens received, and the USDC amount paid. The token was created via Clanker and is viewable on clanker.world. According to the landing page, the endpoint has a 100% success rate with an average latency of 1.28 seconds, though total transaction volume is very low (2 total transactions from 1 unique user at time of crawl).
The x420.dev platform hosts this as a subdomain-based token interaction service. Documentation pages (/docs, /api, /pricing) do not resolve, so details beyond the x402 challenge and landing page are unavailable.
Capabilities
Use cases
- —Programmatically purchasing x105 tokens with USDC via an AI agent or automated workflow
- —Integrating token purchases into x402-compatible payment flows
- —Swapping a custom USDC amount for x105 tokens on Base without a DEX frontend
Fit
Best for
- —Agents that need to acquire x105 tokens programmatically
- —x402-native payment workflows on Base
- —Small USDC-denominated token purchases (up to 5 USDC per call)
Not for
- —Large-volume token purchases exceeding 5 USDC per transaction
- —Users seeking tokens on networks other than Base
- —Anyone needing detailed API documentation or SLA guarantees
Quick start
curl -X POST https://x105.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"amount": "2.5"}'Example
Request
{
"amount": "2.5"
}Response
{
"message": "Successfully purchased x105 tokens",
"tokensReceived": "1250000000000000000",
"usdcAmountPaid": "2.5",
"sendTransactionHash": "0xdef456...",
"swapTransactionHash": "0xabc123..."
}Endpoint
Quality
The x402 challenge is live and includes a well-defined outputSchema with input/output fields. However, there is no OpenAPI spec, no documentation pages resolve, transaction volume is extremely low (2 total), and the response example had to be inferred from the schema. The endpoint is functional but sparsely documented.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all return 'doesn't exist' pages
- —Very low usage: only 2 total transactions from 1 unique user at time of crawl
- —Maximum payment per call is 5 USDC — the 'custom amount' is capped
- —Response example is inferred from outputSchema, not from an actual observed response
- —This involves purchasing a speculative token created via Clanker — exercise caution
Citations
- —The x402 challenge returns maxAmountRequired of 5000000 (5 USDC) and accepts payment on Base networkhttps://x105.x420.dev/api/puff-custom
- —The token contract is 0x51793E001bc1f58E5da3680bD1102EEE0b713B07 and was created via Clankerhttps://x105.x420.dev
- —2 total transactions, 1 unique user, 100% success rate, 1.28s average latencyhttps://x105.x420.dev
- —The amount field defaults to 5 USDC if not providedhttps://x105.x420.dev/api/puff-custom