x402basequality 0.30

x402-gated API platform on Base offering data, AI, finance, and utility endpoints at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

lowpaymentfee.com is an x402-protocol API platform that gates a collection of endpoints behind per-request USDC micropayments on the Base network. The specific endpoint `/api/v1/claims/4` is listed as "Premium API Access" and accepts POST requests with an x402 payment header. The 402 challenge indicates a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The broader platform advertises four categories of APIs: 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 listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The specific functionality behind the `/api/v1/claims/4` endpoint labeled "Premium API Access" is unclear and does not map to any of the named endpoints on the landing page. Agents should treat this as a low-documentation endpoint where the actual response format is unknown until a paid request is made.

Capabilities

x402-paymentusdc-micropaymentbase-networkper-request-billingno-api-keypost-endpoint

Use cases

  • Paying per-request for API access without needing API keys or subscriptions
  • Programmatic agent access to gated endpoints via x402 micropayments on Base
  • Exploring x402 protocol integration patterns for pay-as-you-go services

Fit

Best for

  • Developers or agents wanting zero-signup, pay-per-call API access
  • x402 protocol experimentation and integration testing
  • Scenarios requiring no rate limits and instant access without credentials

Not for

  • Users needing well-documented API schemas and response formats before committing payment
  • High-volume production workloads where per-request crypto payments add latency
  • Anyone without a Base-network USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it accepts payments. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the specific purpose of /api/v1/claims/4 ('Premium API Access') is undefined. The listing is effectively a stub.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet' with no technical content.
  • The endpoint path /api/v1/claims/4 labeled 'Premium API Access' does not correspond to any of the named endpoints on the landing page; its actual functionality is unknown.
  • No OpenAPI spec or request/response schema is provided; callers cannot know the expected input or output format without making a paid request.
  • No robots.txt or agents.txt found on the origin.

Citations

Provenance

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

Agent access