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

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/104`) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 0.02 USDC per request (20,000 base units at 6 decimals). No API keys or rate limits are required; callers simply attach a valid X-PAYMENT header to authorize the micro-payment.

The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services (geocoding, validation, conversion, generation) — all priced at $0.02 per request on Base. However, the specific endpoint being listed here is under the Stripe customers path, which suggests it returns Stripe customer account information for customer ID 104. No OpenAPI schema, request body specification, or response examples are documented in the crawled material.

Because the crawled docs pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive documentation, the actual request format and response structure for this endpoint remain unknown. Callers should expect a JSON response based on the `mimeType` field in the x402 challenge, but the exact fields are unspecified.

Capabilities

x402-paymentusdc-baseper-request-billingstripe-customer-datajson-responseno-api-key

Use cases

  • —Retrieving Stripe customer details for customer ID 104 via a pay-per-call model
  • —Integrating x402 micro-payment flows into agent workflows
  • —Accessing gated financial data without traditional API key provisioning

Fit

Best for

  • —Agents or services that need on-demand Stripe customer data without subscription commitments
  • —Developers experimenting with x402 payment protocol integrations
  • —Scenarios requiring keyless, pay-as-you-go API access on Base

Not for

  • —Bulk retrieval of many Stripe customers (only exposes a single customer ID)
  • —Users who need detailed API documentation or guaranteed SLAs
  • —Applications requiring non-crypto payment methods

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/customers/104
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 for this specific endpoint — no request schema, no response schema, no examples. The docs pages are all empty (wallet-connect only). The endpoint path suggests Stripe customer data for a hardcoded ID, which is unusual and limits general utility.

Warnings

  • —No API documentation available — all doc pages return only a wallet-connect prompt
  • —Endpoint is scoped to a single hardcoded customer ID (104); unclear if this is a demo or production resource
  • —No request body schema or response schema documented anywhere
  • —The broader platform lists many endpoints but none appear to have public documentation

Citations

Provenance

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

Agent access

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