x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 70) 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 maximum amount required per call is 20,000 base units of USDC, which equals $0.02 USD (USDC uses 6 decimals).

The hosting provider, lowpaymentfee.com, advertises a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific endpoint (/api/v1/stripe/customers/70) is not listed on the provider's public catalog page and appears to expose Stripe customer data. The exact response schema is not documented.

Because there is no OpenAPI spec, no detailed documentation, and the crawled docs/pricing/API pages all returned only a "Connect wallet" stub, the actual behavior and response format of this endpoint remain unclear. The endpoint is confirmed live (returns a valid x402 402 challenge), but prospective callers should be aware that the payload structure is undocumented.

Capabilities

x402-paymentusdc-basestripe-customer-dataper-call-pricingno-api-key

Use cases

  • Retrieving Stripe customer information for customer ID 70 via a single paid API call
  • Programmatic access to Stripe customer data without managing API keys
  • Agent-driven workflows that need on-demand Stripe customer lookups settled in USDC

Fit

Best for

  • Agents or services needing one-off Stripe customer data retrieval
  • Developers exploring x402 payment-gated API patterns
  • Use cases where keyless, pay-per-call access is preferred over subscription billing

Not for

  • Bulk Stripe customer data exports (single customer ID only)
  • Users who need detailed API documentation or guaranteed SLAs
  • Production systems requiring well-documented response schemas

Quick start

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

Endpoint

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 OpenAPI spec, no response schema, and all documentation pages return only a wallet-connect stub. The specific endpoint is not listed in the provider's public catalog, and its purpose (exposing a single Stripe customer record) is unusual and undocumented.

Warnings

  • No OpenAPI or response schema available — actual response format is unknown
  • This endpoint exposes Stripe customer data; ensure compliance with data privacy regulations before use
  • Endpoint path references a specific customer ID (70) and is not listed in the provider's public API catalog
  • All documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' stub with no useful content
  • The provider's catalog lists many endpoints but none match this specific path, raising questions about its intended audience

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 10:02:22Z · 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-call in USDC. — Clawmart · Clawmart