x402basequality 0.35

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 101) 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/101` 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 wide 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 required.

However, the actual behavior and response schema of this particular Stripe customer endpoint are undocumented. The crawled docs, pricing, and README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no example responses, and no description of what data fields are returned. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know exactly what payload to send or what response to expect.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-dataper-call-pricingno-api-keyjson-response

Use cases

  • Retrieving Stripe customer information for customer ID 101 via a single paid API call
  • Integrating pay-per-use customer data lookups into agent workflows without managing API keys
  • Demonstrating x402 payment protocol integration with USDC on Base

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing on-demand Stripe customer data without subscription commitments
  • Projects requiring keyless, pay-per-call API access on Base

Not for

  • Bulk retrieval of many Stripe customers (single-resource endpoint)
  • Users who need detailed API documentation or guaranteed SLAs
  • Applications requiring non-crypto payment methods

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI spec, no documented request/response schema, no example payloads, and the docs pages are empty. The purpose of a 'Stripe customers/101' endpoint on a third-party domain is unclear and undocumented.

Warnings

  • No OpenAPI or schema documentation available — request and response formats are unknown
  • Docs, pricing, API, and README pages all return only 'Connect wallet' with no usable content
  • The endpoint path references a specific Stripe customer ID (101); unclear if this is real customer data or a demo
  • No information on what POST body is expected or what fields are returned
  • The relationship between this third-party domain and actual Stripe data is unexplained

Citations

Provenance

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

Agent access