Swap 1 USDC for RUN tokens on Base via x402 payment protocol
What it does
This x402-enabled endpoint on x420.dev allows agents to purchase RUN ($RUN) tokens by paying 1 USDC on the Base network. When a valid X-PAYMENT header is provided, the service executes a token swap and sends the resulting RUN tokens to the caller. The endpoint returns a JSON response containing the swap transaction hash, send transaction hash, the number of tokens received, and the USDC amount paid.
The RUN token (contract 0x7f7F9d18a2b58F808acE9b6db2094E5D9ca33B07) was created via Clanker and is traded on Base. The x402 payment is sent to address 0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd using USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with the "exact" scheme, meaning the full 1 USDC (1000000 in 6-decimal units) is required. The service reports a 100% success rate across 5 total transactions from 2 unique users, with an average latency of 2.28 seconds and a trust score of 83%.
Capabilities
Use cases
- —Autonomous agent purchasing RUN tokens with USDC on Base
- —Programmatic token swaps triggered by x402 micropayments
- —Portfolio diversification bots acquiring meme/community tokens
Fit
Best for
- —AI agents that need to autonomously acquire RUN tokens
- —Developers experimenting with x402 payment-gated token swaps
- —Automated trading strategies on Base network
Not for
- —Large-volume or high-frequency trading (fixed 1 USDC amount, ~2.3s latency)
- —Users seeking tokens on networks other than Base
- —Anyone needing detailed API documentation or customizable swap parameters
Quick start
curl -X GET https://run.x420.dev/api/puff \
-H "X-PAYMENT: <x402-payment-header>"Example
Response
{
"message": "Swap successful",
"tokensReceived": "42000.0",
"usdcAmountPaid": "1.0",
"sendTransactionHash": "0x789abc...012def",
"swapTransactionHash": "0xabc123...def456"
}Endpoint
Quality
No OpenAPI spec, no documentation pages (all return 'doesn't exist'), no examples beyond the x402 challenge output schema. The endpoint is live with a small number of transactions, but information is minimal and largely inferred from the x402 challenge and the landing page stats.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all return 'doesn't exist'
- —Very low transaction volume (5 total, 2 unique users) — limited production validation
- —No OpenAPI schema available; output schema inferred from x402 challenge only
- —RUN is a Clanker-created token with no established market — high financial risk
- —Fixed 1 USDC purchase amount with no apparent configurability
Citations
- —The x402 challenge requires 1,000,000 units (1 USDC) on Base network using the exact schemehttps://run.x420.dev/api/puff
- —The RUN token contract is 0x7f7F9d18a2b58F808acE9b6db2094E5D9ca33B07 and was created via Clankerhttps://run.x420.dev
- —5 total transactions from 2 unique users with 100% success rate and 2.28s average latencyhttps://run.x420.dev
- —Trust score is 83% as reported on the landing pagehttps://run.x420.dev
- —Output schema includes message, swapTransactionHash, sendTransactionHash, tokensReceived, and usdcAmountPaid fieldshttps://run.x420.dev/api/puff