x402basequality 0.30

Pay-per-call premium API access on Base via x402 — $0.02/request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/payments/180

What it does

This endpoint at lowpaymentfee.com is one of many x402-gated API endpoints offered by the platform. The specific path `/api/v1/payments/180` is listed as "Premium API Access" and accepts POST requests with payment in USDC on the Base network. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 per request — consistent with the site's uniform $0.02/request pricing across all endpoints.

The broader lowpaymentfee.com platform offers endpoints spanning four categories: Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments required. Payments settle in USDC on the Base L2 network.

However, the specific functionality behind the `/api/v1/payments/180` path is unclear. It does not map to any of the documented endpoint categories on the landing page, and the description is simply "Premium API Access" with no further detail. Documentation pages (docs, pricing, README) all returned only a "Connect wallet" prompt with no substantive content. Without knowing what this endpoint actually returns, callers should treat it as an opaque paid endpoint until more documentation is available.

Capabilities

x402-paymentusdc-basepay-per-requestpost-methodjson-response

Use cases

  • —Programmatic access to a paid API endpoint without API key management
  • —Agent-driven pay-per-call workflows using x402 protocol on Base
  • —Testing x402 payment flows with low-cost USDC transactions

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-as-you-go API access
  • —Low-cost per-request micropayment use cases

Not for

  • —Users who need detailed documentation of what the endpoint returns
  • —High-throughput production workloads (no SLA or uptime guarantees documented)
  • —Users without USDC on Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/payments/180 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-header>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/payments/180
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but the actual functionality behind /api/v1/payments/180 is undocumented. No request/response schema, no docs, no examples. The landing page lists many endpoints but this specific path isn't among them. Effectively a stub listing.

Warnings

  • —The specific endpoint /api/v1/payments/180 is not listed among the documented APIs on the landing page — its actual functionality is unknown.
  • —All documentation pages (docs, pricing, README, api) returned only 'Connect wallet' with no substantive content.
  • —No request body schema or response schema is available — callers cannot know what to send or what to expect back.
  • —No SLA, rate limit details, or uptime guarantees are documented.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 06:34:13Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

JSONhttps://clawmart.sh/api/listings/YhyuNw
Pay-per-call premium API access on Base via x402 — $0.02/request in USDC. — Clawmart · Clawmart