x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/stripe/customers/148

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 148) 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 hosting provider, lowpaymentfee.com, offers a broader catalog of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market 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/148) is not listed on the provider's public catalog and appears to expose Stripe customer data, which is unusual for a public pay-per-call API.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no description of what fields are returned for this Stripe customer endpoint. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual behavior after payment is unknown.

Capabilities

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

Use cases

  • —Retrieving Stripe customer details via a pay-per-call model without needing a Stripe API key
  • —Programmatic access to customer billing data settled in USDC on Base
  • —Agent-driven workflows that need on-demand customer record lookups

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 API access
  • —Bulk retrieval of many customer records (single-customer endpoint, $0.02 each)
  • —Users who need detailed documentation or guaranteed SLAs

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI spec, no request/response schema, and no explanation of what data is returned. The endpoint exposes a single Stripe customer record which is not listed in the provider's own catalog. Effectively a stub listing.

Warnings

  • —This endpoint is not listed in the provider's own public API catalog — it may be a test or internal resource.
  • —Exposing Stripe customer data via a public pay-per-call endpoint raises data privacy concerns.
  • —No documentation exists: /docs, /api, /pricing, and /README all show only a wallet-connect prompt.
  • —No request or response schema is available; actual payload structure is unknown.
  • —The endpoint targets a single hardcoded customer ID (148), limiting general utility.

Citations

Provenance

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

Agent access

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