x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/85`) behind an x402 paywall. It accepts GET requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance/crypto feeds, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here (`/stripe/customers/85`) is not featured on the site's public catalog; it appears to be a Stripe customer record lookup. No OpenAPI schema, detailed documentation, or example responses are available for this endpoint — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content.

Because there is no documentation describing the response shape or the nature of the data returned, agents should treat this endpoint with caution. The x402 challenge is live and well-formed, confirming the endpoint is operational, but the actual utility of the returned payload is unknown.

Capabilities

x402-paymentusdc-basestripe-customer-datapay-per-requestjson-response

Use cases

  • Retrieving Stripe customer record #85 via a single paid GET request
  • Demonstrating x402 payment-gated API access on Base
  • Programmatic access to customer data without API key management

Fit

Best for

  • Agents or developers needing on-demand Stripe customer data without subscription
  • x402 protocol experimentation and integration testing
  • Micropayment-based API consumption on Base L2

Not for

  • Bulk Stripe data exports or batch customer queries
  • Use cases requiring documented response schemas or SLAs
  • Users who need access to arbitrary Stripe customer IDs (this endpoint is fixed to ID 85)

Quick start

curl -H "X-PAYMENT: <x402_payment_token>" https://lowpaymentfee.com/api/v1/stripe/customers/85

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint works. However, there is no OpenAPI spec, no response schema, no example responses, and the docs pages are empty ("Connect wallet" only). The specific endpoint (/stripe/customers/85) is not listed in the site's public catalog, making its purpose unclear. Effectively a stub listing.

Warnings

  • No documentation or response schema available for this specific endpoint
  • Endpoint path references a hardcoded Stripe customer ID (85) — unclear if other IDs are supported
  • Docs, pricing, API, and README pages render only 'Connect wallet' with no usable content
  • The /stripe/customers/ path is not listed in the site's public API catalog

Citations

Provenance

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

Agent access

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