x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

lowpaymentfee.com is an x402-protocol API marketplace that gates access to a variety of endpoints behind per-request USDC micropayments on the Base network. The specific endpoint at `/api/v1/stripe/charges/55` is labeled "Premium API Access" and requires up to $0.02 in USDC (20,000 base units with 6 decimals) per call, settled on-chain to a specified wallet address. No API keys, rate limits, or upfront commitments are required — callers simply attach an X-PAYMENT header conforming to the x402 exact-payment scheme.

The broader platform advertises four categories of endpoints: 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 are listed at the same $0.02/request price point. However, the specific endpoint being listed here (`/api/v1/stripe/charges/55`) does not clearly map to any of these advertised categories — its path suggests it may relate to Stripe charge processing or a test/demo endpoint.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for any endpoint. The x402 challenge is live and well-formed, confirming the endpoint is operational, but what it actually returns upon successful payment is unknown.

Capabilities

x402-paymentusdc-micropaymentbase-networkper-request-billingno-api-keyjson-response

Use cases

  • Paying per-request for API access without needing API keys or subscriptions
  • Programmatic agent access to gated endpoints using x402 on-chain payments
  • Testing x402 payment protocol integrations against a live endpoint

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need keyless, pay-as-you-go API access on Base
  • Projects wanting to avoid API key management and rate limits

Not for

  • Production workloads requiring documented, well-specified API contracts
  • Users who need detailed response schemas and error handling documentation
  • Anyone without a Base-network USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint is operational at $0.02 USDC per request. However, documentation is essentially nonexistent — no OpenAPI spec, no request/response examples, no explanation of what this specific endpoint does. The endpoint path ('stripe/charges/55') doesn't match any of the advertised API categories, raising questions about its actual purpose.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README pages all return only a 'Connect wallet' prompt with no content.
  • No OpenAPI or schema definition exists for any endpoint.
  • The endpoint path '/api/v1/stripe/charges/55' does not correspond to any of the advertised API categories (Data, AI, Finance, Infrastructure); its actual function is unclear.
  • No request body schema or response schema is documented; callers cannot know what to send or what to expect back.
  • The '55' in the path may be an arbitrary resource ID; it is unclear if other IDs are valid.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 09:38:11Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access