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

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/167`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance, and utility categories, all settled on the Base network using USDC. The specific endpoint listed here appears to return Stripe customer data for customer ID 167.

The x402 challenge confirms the endpoint is live and accepts payment via the "exact" scheme on Base mainnet. The maximum amount required is 20,000 base units of USDC (token contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), which equals $0.02 USD (USDC uses 6 decimals). Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout. The endpoint accepts HTTP POST requests.

Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the Stripe customer endpoint returns or what POST body it expects. The provider's landing page lists many other endpoints at $0.02 each but does not include this specific Stripe customers path among them, making its purpose somewhat unclear. It may be a demonstration or internal endpoint.

Capabilities

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

Use cases

  • —Retrieving Stripe customer details via a per-call USDC micropayment
  • —Demonstrating x402 payment protocol integration with real endpoints
  • —Accessing API data without traditional API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand Stripe customer lookups without subscription commitments
  • —Low-volume, pay-as-you-go API consumption on Base

Not for

  • —High-volume Stripe data access (no documented rate limits but micropayment overhead per call)
  • —Users needing detailed API documentation or guaranteed SLAs
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and confirms pricing and network details, but there is zero documentation on request format, response schema, or what this specific Stripe customer endpoint actually returns. Docs pages are empty beyond a wallet-connect prompt. The endpoint path is not listed among the provider's advertised APIs, adding uncertainty about its purpose.

Warnings

  • —No OpenAPI schema or request/response documentation available
  • —Docs, pricing, API, and README pages all render only 'Connect wallet' with no content
  • —This specific endpoint (/api/v1/stripe/customers/167) is not listed among the provider's advertised APIs on the landing page
  • —Purpose and response format of the Stripe customer endpoint are entirely unknown
  • —Hardcoded customer ID (167) in the path suggests this may be a demo or single-resource endpoint

Citations

Provenance

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

Agent access

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