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/135

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/135`) 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 at 6 decimals equals $0.02 USD.

The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the Stripe customers endpoint, whose exact response payload is not documented. The endpoint path suggests it returns information about a particular Stripe customer record (ID 135).

No OpenAPI schema, detailed documentation, or example responses were found in the crawl. The docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no substantive content. Because the actual data returned by this endpoint is undocumented and the purpose of exposing a single Stripe customer record is unclear, users should treat this as an experimental or lightly-documented service.

Capabilities

x402-paymentusdc-basepay-per-requeststripe-customer-datajson-responseno-api-key

Use cases

  • —Retrieving Stripe customer information via a pay-per-call model
  • —Programmatic access to customer records without traditional API key management
  • —Agent-driven lookups of Stripe customer data settled in USDC on Base

Fit

Best for

  • —Developers wanting keyless, pay-per-request access to Stripe customer data
  • —AI agents that can settle x402 payments on Base
  • —Prototyping micropayment-gated API workflows

Not for

  • —Production Stripe integrations where you already have direct Stripe API access
  • —Use cases requiring documented response schemas and SLAs
  • —High-volume batch retrieval of many customer records

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no example request/response, and the purpose of exposing a single Stripe customer record is unclear. Docs pages returned only wallet-connect prompts.

Warnings

  • —No documentation or OpenAPI schema available — response format is unknown
  • —The endpoint exposes a single hardcoded Stripe customer ID (135); purpose and data sensitivity are unclear
  • —All doc/pricing/API pages render only a 'Connect wallet' prompt with no substantive content
  • —Potential data privacy concern: endpoint may expose customer PII from Stripe

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

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