Buy PAMP tokens with USDC via x402 payment on Base network
What it does
This x402 endpoint allows agents and users to purchase PAMP tokens (contract 0xFC265F5385625AEb988AB46B1e7FB37AcE6a6b07) by spending USDC on the Base network. The endpoint accepts a POST request with an optional `amount` field specifying how much USDC to spend (defaults to 5 USDC if omitted). The maximum payment accepted per call is 5 USDC (maxAmountRequired: 5000000 in 6-decimal USDC units). Upon successful payment and swap, the response includes the swap transaction hash, send transaction hash, tokens received, and USDC amount paid.
The token was created via Clanker and is hosted on the x420.dev platform, which appears to provide x402-enabled subdomains for token interactions. On-chain stats from the landing page show 3 total transactions, 1 unique user, average latency of 2.61 seconds, and a 100% success rate. The endpoint uses the x402 "exact" payment scheme with USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) as the payment asset, paying to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd. No separate documentation or pricing pages exist beyond the landing page and the x402 challenge itself.
Capabilities
Use cases
- —Autonomous agent purchasing PAMP tokens with USDC via x402 protocol
- —Programmatic token swaps on Base network without manual wallet interaction
- —Integrating on-chain token purchases into agent workflows
Fit
Best for
- —AI agents that need to autonomously buy tokens on Base
- —Developers building x402-compatible payment flows for DeFi
- —Automated trading or accumulation strategies for PAMP token
Not for
- —Purchasing tokens on networks other than Base
- —Swapping tokens other than USDC to PAMP
- —Users needing detailed swap routing or slippage controls
Quick start
curl -X POST https://pamp.x420.dev/api/puff-custom \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"amount": "5"}'Example
Request
{
"amount": "5"
}Response
{
"message": "Successfully swapped USDC for PAMP tokens",
"tokensReceived": "1000000",
"usdcAmountPaid": "5.0",
"sendTransactionHash": "0x789ghi...jkl012",
"swapTransactionHash": "0xabc123...def456"
}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 page (docs/api/pricing all return 'doesn't exist'), very low usage (3 total transactions, 1 unique user), and the response example is inferred from the outputSchema rather than observed. The token itself is a Clanker-created meme token with minimal adoption.
Warnings
- —No documentation pages exist beyond the landing page
- —Very low usage: only 3 total transactions from 1 unique user
- —Response example is inferred from outputSchema, not from actual observed responses
- —PAMP is a Clanker-created token with no established market or liquidity guarantees
- —Max amount per call is 5 USDC (5000000 in 6-decimal units)
Citations
- —The x402 challenge returns status 402 with maxAmountRequired of 5000000 on Base network using USDC asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://pamp.x420.dev/api/puff-custom
- —3 total transactions, 1 unique user, 2.61s average latency, 100% success rate, 82% trust scorehttps://pamp.x420.dev
- —Token created by 0x42e9...1927 and viewable on Clankerhttps://pamp.x420.dev
- —Token contract address is 0xFC265F5385625AEb988AB46B1e7FB37AcE6a6b07https://pamp.x420.dev
- —x402scan listing for recipient 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbdhttps://www.x402scan.com/recipient/0x93109d14f6665a9c9675290d3cd5a6c07bbafdbd/resources