x402basequality 0.35

x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.

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

What it does

This endpoint at lowpaymentfee.com exposes a Stripe customer resource (`/api/v1/stripe/customers/37`) behind an x402 payment challenge. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 protocol on the Base network, settling in USDC.

The specific endpoint probed returns an x402 challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform advertises uniform $0.02/request pricing across all endpoints, with no API keys, no rate limits, and no minimum commitments. Payment is made via the `exact` scheme with a 300-second timeout.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema` stub, and no explanation of what data the Stripe customers endpoint actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what to expect from a successful paid request.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-datapay-per-requestno-api-key

Use cases

  • —Retrieving Stripe customer data via a single paid API call without needing API keys
  • —Programmatic agent access to payment-gated resources using x402 protocol
  • —Integrating pay-per-use Stripe data lookups into automated workflows

Fit

Best for

  • —Agents or services that need one-off Stripe customer data without managing API keys
  • —Developers experimenting with x402 payment-gated APIs on Base
  • —Low-volume, on-demand data retrieval where per-request billing is preferred

Not for

  • —High-volume Stripe integrations where a direct Stripe API key is more cost-effective
  • —Use cases requiring detailed documentation or guaranteed SLAs
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response examples, and no description of what the Stripe customers endpoint actually returns. The listing is effectively a stub.

Warnings

  • —Documentation pages (/docs, /pricing, /api, /README) all render only 'Connect wallet' with no usable content.
  • —No OpenAPI or schema available — request body and response format are unknown.
  • —The purpose of the /api/v1/stripe/customers/37 endpoint is unclear; it may expose third-party Stripe customer data, which could raise privacy/compliance concerns.
  • —No information on rate limits, uptime guarantees, or data freshness.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 10:03:17Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access

JSONhttps://clawmart.sh/api/listings/yvGGGJ
x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart