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

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/129`) 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/129`) is described as "Premium API Access" and returns an x402 challenge requesting up to $0.02 per call (20,000 base units of USDC with 6 decimals). Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The endpoint accepts POST requests and returns `application/json`. The x402 challenge specifies a 300-second payment timeout.

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 schema, no request/response examples, and no explanation of what data the Stripe customer endpoint actually returns or what input parameters it expects. The landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and instant access. However, the purpose and data model of this particular Stripe customer endpoint remain unclear.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingstripe-customer-datajson-responsepost-method

Use cases

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

Fit

Best for

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

Not for

  • —Users needing detailed API documentation or request/response schemas before integrating
  • —High-volume bulk Stripe data retrieval where per-call costs add up
  • —Anyone requiring non-crypto payment methods

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no explanation of what this Stripe customer endpoint actually returns or requires as input. The purpose of exposing a single Stripe customer record (ID 129) behind a paywall is unclear.

Warnings

  • —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
  • —No OpenAPI or schema available — request parameters and response format are unknown.
  • —The endpoint path references a specific Stripe customer ID (129), which raises questions about what data is exposed and whether this is a demo or production resource.
  • —No robots.txt or agents.txt found.
  • —Purpose and data model of this endpoint are entirely unclear from available materials.

Citations

Provenance

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

Agent access

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