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

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/174`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC via the x402 protocol.

The specific endpoint probed (`/api/v1/stripe/customers/174`) is described as "Premium API Access" and returns a 402 challenge requesting up to $0.02 USDC (20,000 base units of USDC with 6 decimals) per call. It accepts HTTP POST requests and returns `application/json`. Payment is sent to `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on the Base L2 network, with a 300-second timeout window.

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 examples of what the endpoint actually returns. The provider's landing page advertises uniform $0.02/request pricing, no API keys, no rate limits, and instant access across all endpoints. Without documentation on what data this Stripe customers endpoint returns or what input it expects, practical usage requires experimentation.

Capabilities

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

Use cases

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

Fit

Best for

  • —Developers wanting keyless, pay-per-call access to Stripe customer data
  • —AI agents that can settle x402 payments on Base in USDC
  • —Users who prefer crypto micropayments over subscription billing

Not for

  • —Anyone needing documented request/response schemas before integration
  • —Bulk or high-volume Stripe data retrieval (no batch endpoint documented)
  • —Users without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is zero documentation on request parameters, response schema, or what 'Premium API Access' to Stripe customer 174 actually returns. The docs/pricing/README pages are all blank wallet-connect stubs. No OpenAPI spec exists. The listing is effectively a stub.

Warnings

  • —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content
  • —No request or response schema documented; unknown what data this endpoint returns
  • —The endpoint references a specific Stripe customer ID (174), which may be a demo or placeholder
  • —No OpenAPI or machine-readable spec provided by the server

Citations

Provenance

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

Agent access

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