Pay 1 USDC via x402 to swap for MON tokens on Base network
What it does
This x402-enabled endpoint allows agents and users to purchase MON ($MON) tokens by paying 1 USDC on the Base network. The endpoint is hosted on x420.dev, a platform for creating x402-payable token swap services tied to Clanker-launched tokens.
When a valid x402 payment header containing 1 USDC (1,000,000 units at 6 decimals) is sent as a GET request, the service executes a swap from USDC to MON tokens (contract 0x4DA4C8349bAe3f9986A56Dba62cDB583fA91cb07) and sends the resulting tokens to the buyer. The response includes the swap transaction hash, send transaction hash, the amount of tokens received, and the USDC amount paid.
The MON token was created via Clanker (a Base-native token launcher) by address 0x2141...e1Ee. The payment is routed to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd using USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. No documentation, OpenAPI spec, or agents.txt is available beyond the x402 challenge metadata and the landing page.
Capabilities
Use cases
- —Autonomous agent purchasing MON tokens using USDC via x402 protocol
- —Programmatic token acquisition on Base network without manual wallet interaction
- —Integrating token swaps into agent workflows that support x402 payment headers
Fit
Best for
- —AI agents with x402 payment capability looking to acquire specific tokens
- —Developers experimenting with x402 protocol for on-chain token swaps
- —Automated trading or portfolio strategies involving Clanker-launched tokens
Not for
- —Users needing large or variable-amount token swaps (fixed at 1 USDC)
- —Anyone seeking detailed API documentation or OpenAPI specs
- —Production trading systems requiring guaranteed execution or SLAs
Quick start
curl -X GET https://mon.x420.dev/api/puff \
-H "X-PAYMENT: <x402-payment-header-with-1-USDC-on-Base>"Example
Response
{
"message": "Successfully swapped USDC for MON tokens",
"tokensReceived": "1500000000000000000000",
"usdcAmountPaid": "1000000",
"sendTransactionHash": "0x789ghi...jkl012",
"swapTransactionHash": "0xabc123...def456"
}Endpoint
Quality
No OpenAPI spec, no documentation pages (all return 'doesn't exist'), and no usage examples are provided. The only structured information comes from the x402 challenge response and the sparse landing page. The output schema is inferred from the x402 challenge metadata. The endpoint appears live but is minimally documented.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all return placeholder pages
- —No OpenAPI or agents.txt specification provided
- —Fixed 1 USDC payment amount with no apparent configurability
- —Token swap involves an unaudited Clanker-launched token — high financial risk
- —Response example is entirely inferred from the outputSchema in the x402 challenge; no real response was observed
- —maxTimeoutSeconds is 120, suggesting swap execution may be slow
Citations
- —The x402 challenge requires 1,000,000 units (1 USDC) payment on Base network to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbdhttps://mon.x420.dev/api/puff
- —MON token contract address is 0x4DA4C8349bAe3f9986A56Dba62cDB583fA91cb07, created via Clanker by 0x2141...e1Eehttps://mon.x420.dev
- —USDC asset address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://mon.x420.dev/api/puff
- —Output schema includes message, swapTransactionHash, sendTransactionHash, tokensReceived, and usdcAmountPaid fieldshttps://mon.x420.dev/api/puff