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

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/122`) behind an x402 paywall. It 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). No API keys or rate limits are advertised; access is granted purely through on-chain micropayment.

The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request on the Base network. However, this specific listing is for the Stripe customer endpoint, which appears to return customer-level data from Stripe. The exact response schema is not documented; the crawled docs, pricing, and README pages all render only a "Connect wallet" prompt with no further detail.

Because there is no OpenAPI spec, no response schema, and no documentation beyond the landing page's brief catalog, the actual fields returned by this endpoint are unknown. Callers should expect a JSON payload related to Stripe customer #122 but must discover the structure empirically.

Capabilities

x402-paymentusdc-basestripe-customer-dataper-call-micropaymentno-api-keyjson-response

Use cases

  • —Retrieving Stripe customer information via a single micropayment without needing an API key
  • —Agent-driven workflows that need on-demand access to customer billing data
  • —Demonstrating x402 payment protocol integration with real endpoints

Fit

Best for

  • —Developers experimenting with x402 payment flows on Base
  • —Agents that need keyless, pay-per-call access to Stripe customer data
  • —Low-volume, on-demand lookups where subscription billing is overkill

Not for

  • —High-volume Stripe integrations where direct Stripe API access is cheaper
  • —Use cases requiring full Stripe API coverage (refunds, charges, subscriptions, etc.)
  • —Users without a Base-network USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no response schema, no request body documentation, and the docs/pricing/README pages all render only a wallet-connect prompt. The purpose of exposing a single Stripe customer record behind a paywall is unclear and undocumented.

Warnings

  • —No OpenAPI or response schema available — callers must discover the response format empirically.
  • —Documentation pages (/docs, /pricing, /README, /api) all render only 'Connect wallet' with no useful content.
  • —The endpoint exposes a specific Stripe customer ID (122); the scope and sensitivity of the returned data is unknown.
  • —The purpose of proxying a single Stripe customer record through a public paywall is unclear and may raise data-privacy concerns.

Citations

Provenance

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

Agent access

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