x402basequality 0.30

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

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 184) behind an x402 payment wall. 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 specific endpoint `/api/v1/stripe/customers/184` is listed as "Premium API Access" and costs up to 20,000 base units of USDC (i.e., $0.02 given USDC's 6 decimals) per request. The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing across a wide catalog of endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities. The platform emphasizes no API keys, no rate limits, and instant access — all gated purely by x402 micropayments.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the Stripe customer endpoint actually returns. The exact nature of the data served (whether it proxies live Stripe data, returns mock data, or something else) cannot be determined from available materials.

Capabilities

x402-paymentusdc-basestripe-customer-dataper-request-billingno-api-key

Use cases

  • —Retrieving Stripe customer information via a single micropayment without API key management
  • —Agent-driven access to customer billing data with per-call USDC settlement
  • —Programmatic lookup of Stripe customer records gated by crypto micropayments

Fit

Best for

  • —Agents or services that need on-demand Stripe customer data without subscription commitments
  • —Developers experimenting with x402 payment-gated API patterns
  • —Use cases requiring keyless, pay-as-you-go access to financial data

Not for

  • —Production Stripe integrations where you already have direct Stripe API access
  • —High-volume batch retrieval of many customer records (each call costs $0.02)
  • —Users who need detailed documentation or guaranteed SLAs

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (returns a valid x402 402 challenge) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of this specific Stripe customer endpoint is opaque — it's unclear what data it returns or what input it expects beyond a POST. The docs pages are all empty wallet-connect stubs.

Warnings

  • —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
  • —No OpenAPI or schema definition for request or response payloads
  • —The endpoint references a specific Stripe customer ID (184); unclear if this is real customer data, a demo, or a proxy
  • —Purpose and data returned by this endpoint cannot be verified from available materials
  • —May involve regulated financial/PII data (Stripe customer records) — verify compliance requirements

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 10:01:53Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access

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