x402basequality 0.15

Buy custom USDC amounts of $RUN tokens via x402 payment protocol on Base

Price
5.00 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at run.x420.dev allows agents and users to purchase a custom USDC amount worth of $RUN (RUNNER) tokens. The $RUN token is deployed at contract address 0x7f7F9d18a2b58F808acE9b6db2094E5D9ca33B07 and was created via the Clanker token launcher on Base. The endpoint is part of the x420.dev platform, which wraps token purchases behind x402 paywalled HTTP endpoints.

Based on the landing page, the service reports an average latency of 2.28 seconds, a 100% success rate across 5 total transactions from 2 unique users, and a trust score of 83%. The UI exposes a "Puff" action where users enter a USDC amount to spend. However, the probe did not return a standard 402 challenge from the endpoint (it returned 405), and no OpenAPI schema, documentation pages, or API reference exist — the /docs, /api, /pricing, and /README paths all resolve to placeholder pages.

Without a formal schema or documented request/response format, integration details must be inferred. The endpoint likely accepts a USDC amount and executes a token swap, but exact parameters, authentication flow, and response structure are unknown.

Capabilities

token-purchasex402-paymentusdc-to-token-swapbase-chainclanker-token

Use cases

  • Programmatically purchasing $RUN tokens with USDC via an HTTP call
  • Agent-driven token acquisition using the x402 payment protocol
  • Automating small token buys on Base chain without direct DEX interaction

Fit

Best for

  • Agents or bots that need to acquire $RUN tokens programmatically
  • Developers experimenting with x402 payment-gated endpoints
  • Users who want a simple HTTP-based token purchase flow

Not for

  • Production trading or large-volume token swaps requiring reliable documentation
  • Users needing tokens other than $RUN
  • Anyone requiring a well-documented, schema-validated API

Quick start

# No formal schema available. Based on the UI, the endpoint likely accepts a USDC amount.
# The x402 protocol typically requires a payment header.
curl -X POST https://run.x420.dev/api/puff-custom \
  -H "Content-Type: application/json" \
  -d '{"amount": "1.00"}'

Endpoint

Transporthttp
Protocolx402
Pay to0x93109d14F6665a9c9675290D3cD5A6c07bBAfdbd
CurrencyUSD COIN

Quality

0.15/ 1.00

The probe returned a 405 (not 402) from the endpoint, no OpenAPI schema exists, and all documentation paths return placeholder pages. Only the landing page provides any information, and it is minimal. Request/response formats are entirely unknown.

Warnings

  • Endpoint returned HTTP 405 instead of the expected 402 challenge during probing
  • No API documentation, OpenAPI schema, or formal specification available
  • All /docs, /api, /pricing, /README paths resolve to 'doesn't exist' placeholder pages
  • Only 5 total transactions recorded with 2 unique users — very low usage
  • Token is a Clanker-launched meme token; exercise caution regarding liquidity and value
  • Request and response schemas are completely unknown and had to be omitted

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 18:35:40Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access