x402basequality 0.30

x402-gated premium API access on Base, paid per-call in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 paywall. The provider operates a suite of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3 data, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required; callers simply attach an x402 payment header to each request.

The specific endpoint `/api/v1/stripe/charges/114` is listed under the title "Premium API Access." Its x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. The endpoint accepts HTTP POST and returns application/json.

Documentation beyond the landing page 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, and no description of what this particular endpoint actually returns. The name "stripe/charges/114" suggests it may relate to Stripe charge data or a payment-processing wrapper, but this is speculative. Prospective callers should be aware that the actual functionality behind this endpoint is undocumented.

Capabilities

x402-paymentusdc-basepay-per-calljson-responsehttp-post

Use cases

  • Programmatic access to a premium API endpoint with per-call USDC micropayments
  • Agent-driven workflows that need keyless, on-demand API access without subscriptions
  • Testing x402 payment flows on Base network

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents that need frictionless pay-per-call API access without API key management
  • Low-volume consumers who prefer micropayments over subscriptions

Not for

  • Users who need well-documented API contracts and response schemas before integrating
  • High-volume production workloads where per-call crypto settlement overhead matters
  • Anyone who needs to understand the exact response format before paying

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/114 \
  -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 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation of what the endpoint actually does or returns, and the docs/pricing/README pages are all empty wallet-connect stubs. The endpoint name 'stripe/charges/114' is opaque without further context.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or schema describing request parameters or response format.
  • The purpose of '/api/v1/stripe/charges/114' is unclear; 'Premium API Access' is a generic label that does not describe functionality.
  • No examples of successful responses are available anywhere in the crawled material.

Citations

Provenance

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

Agent access