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
Endpoint
https://lowpaymentfee.com/api/v1/stripe/customers/185

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 185) 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 (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a range of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and instant access. However, this specific listing is for the `/api/v1/stripe/customers/185` endpoint, which appears to expose Stripe customer data. The exact response schema is not documented; the only metadata available is the x402 challenge and the site's landing page.

Documentation is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no example request/response documentation, and no description of what fields the Stripe customer endpoint returns. The endpoint is confirmed live (returns 402 with a valid x402 challenge), but the lack of documentation makes it difficult to know what data is actually served.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-dataper-call-pricingno-api-key

Use cases

  • —Retrieving Stripe customer details via a pay-per-call model without needing an API key
  • —Programmatic access to customer payment data settled in USDC on Base
  • —Agent-driven workflows that need Stripe customer info with crypto-native payment

Fit

Best for

  • —Developers who want keyless, pay-per-request access to Stripe customer data
  • —AI agents with USDC on Base that need to fetch customer records
  • —Prototyping integrations where traditional Stripe API key management is undesirable

Not for

  • —Production Stripe integrations where you already have direct Stripe API access
  • —Use cases requiring bulk customer data retrieval (single-customer endpoint)
  • —Users without USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 challenge, but documentation is essentially nonexistent — /docs, /pricing, /api, and /README all show only 'Connect wallet'. There is no OpenAPI spec, no example responses, and no description of what the Stripe customer endpoint actually returns. The purpose of exposing a single Stripe customer record via x402 is unclear.

Warnings

  • —No documentation available — all doc pages render only 'Connect wallet'
  • —No OpenAPI or response schema provided; response format is unknown
  • —Endpoint exposes a specific Stripe customer ID (185) — unclear if this is real customer data or a demo
  • —Potential data privacy concern: exposing Stripe customer records through a public paywall

Citations

Provenance

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

Agent access

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