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

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/132`) 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/132`) is described by the provider simply as "Premium API Access" and returns JSON. It accepts POST requests and charges up to $0.02 per call (20,000 base units of USDC with 6 decimals). Payment is made via the x402 exact scheme to the provider's wallet on Base. No API keys or rate limits are advertised; access is gated entirely by the on-chain micropayment.

Documentation is extremely thin — 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 data this particular endpoint actually returns. The endpoint is live (returns a proper 402 challenge), but without documentation it is unclear what request body is expected or what the response payload looks like. The broader site lists many endpoints at $0.02 each, but this specific Stripe customers endpoint is not listed on the homepage, making its purpose ambiguous.

Capabilities

x402-paymentusdc-settlementbase-networkper-request-pricingjson-responsestripe-customer-data

Use cases

  • —Retrieving Stripe customer data via a pay-per-call model without API key management
  • —Programmatic agent access to premium data endpoints settled on-chain
  • —Integrating micropayment-gated services into automated workflows

Fit

Best for

  • —Agents or developers who want keyless, pay-per-use API access
  • —Use cases requiring on-chain payment settlement on Base
  • —Scenarios where traditional subscription billing is undesirable

Not for

  • —Users needing detailed API documentation or request/response schemas before integrating
  • —High-volume use cases where per-request pricing may add up without bulk discounts
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/customers/132
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, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the endpoint's specific purpose (Stripe customer 132) is unexplained. This is effectively a stub listing.

Warnings

  • —No documentation available — all doc/pricing/API/README pages render only 'Connect wallet'
  • —No OpenAPI or request/response schema provided
  • —The specific endpoint /api/v1/stripe/customers/132 is not listed among the provider's advertised APIs on the homepage
  • —Purpose and expected input/output of this endpoint are unknown
  • —Exposing Stripe customer data via a public paywall raises potential data privacy concerns

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 09:49:07Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access

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