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, settling payments in USDC on the Base network. The specific endpoint `/api/v1/stripe/charges/96` is one of many offered by the provider, which hosts a broad catalog spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints share a uniform $0.02-per-request pricing model with no API keys, no rate limits, and no minimum commitments.

The x402 challenge confirms the endpoint is live, accepting POST requests and requiring an X-PAYMENT header. Payment is made in USDC (contract 0x8335…2913 on Base) to address 0x1A2B…85F3, with a maxAmountRequired of 20000 base units (i.e., $0.02 given USDC's 6 decimals). The timeout is 300 seconds. The endpoint returns application/json responses.

Documentation is extremely thin — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the endpoint actually returns. The name "stripe/charges/96" suggests it may relate to Stripe charge data or a proxy for payment processing, but this is speculative. Without documentation, the actual functionality of this specific endpoint remains unclear.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingno-api-keyjson-responsepost-method

Use cases

  • Programmatic access to premium API services without traditional API key management
  • Agent-driven workflows that need pay-per-call access settled in USDC on Base
  • Accessing data, AI, finance, or utility endpoints with no subscription commitment

Fit

Best for

  • Developers or agents wanting frictionless per-request billing in crypto
  • Use cases requiring no rate limits and instant access without signup
  • x402-compatible agent toolchains on the Base network

Not for

  • Users who need detailed API documentation or response schema guarantees before integrating
  • High-volume use cases where per-request pricing at $0.02 may be expensive compared to bulk plans
  • Anyone requiring fiat-only payment rails

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/charges/96 \
  -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 confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response examples, and the actual functionality of this specific endpoint (stripe/charges/96) is undocumented and unclear. The docs, pricing, and README pages are all empty beyond a wallet connect prompt.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • The specific purpose of /api/v1/stripe/charges/96 is undocumented — the name suggests Stripe charge data but this is unverified
  • All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no usable content
  • No request body schema or response schema is documented anywhere
  • The provider lists many endpoints but none have detailed documentation

Citations

Provenance

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

Agent access