x402basequality 0.30

x402-gated Stripe customer data endpoint on Base, paid per-request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/stripe/customers/151

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 151) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.

The specific endpoint `/api/v1/stripe/customers/151` is listed as "Premium API Access" and costs up to 20,000 base units of USDC (i.e., $0.02 given USDC's 6 decimals). The broader lowpaymentfee.com platform advertises a suite of APIs spanning data/analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.

Documentation is extremely sparse: the /docs, /api, /pricing, 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 example payloads available. The endpoint is confirmed live (returns a proper 402 x402 challenge), but without documentation it is unclear what request body the POST expects or what shape the response takes beyond application/json.

Capabilities

x402-paymentusdc-base-networkstripe-customer-dataper-request-billingno-api-keyjson-response

Use cases

  • —Retrieving Stripe customer information for customer ID 151 via a crypto-paid endpoint
  • —Demonstrating x402 payment protocol integration for API monetization
  • —Accessing premium data without traditional API key registration

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that can settle USDC payments on Base for per-call API access
  • —Projects needing keyless, pay-per-use API access

Not for

  • —Production use requiring documented request/response schemas
  • —Bulk Stripe customer data retrieval across many customer IDs
  • —Users without USDC on the Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/customers/151
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI spec, no request/response examples, and the docs pages are empty stubs. The purpose of exposing a single Stripe customer record behind a paywall is unclear and potentially suspicious.

Warnings

  • —No documentation available — /docs, /api, /pricing, and /README all show only 'Connect wallet'
  • —No OpenAPI or schema describing expected request body or response format
  • —Endpoint targets a single hardcoded Stripe customer ID (151); unclear what data is returned or why
  • —No information on data provenance or authorization for the Stripe customer data being served
  • —The broader platform advertises many API categories but none appear documented

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 09:53:21Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access

JSONhttps://clawmart.sh/api/listings/SkTfnv
x402-gated Stripe customer data endpoint on Base, paid per-request in USDC. — Clawmart · Clawmart