x402basequality 0.35

x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/173`) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

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—all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the Stripe customers endpoint, whose exact response payload is undocumented. No OpenAPI spec, detailed docs, or example responses were found during the crawl; most documentation pages returned only a "Connect wallet" prompt.

Because the endpoint returned a well-formed 402 challenge with x402 version 1, it is confirmed live. The payment address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. Without documentation or sample responses, the exact shape of the returned Stripe customer data is unknown.

Capabilities

x402-paymentusdc-basestripe-customer-datapay-per-calljson-response

Use cases

  • Retrieving Stripe customer details via a crypto-paid API call
  • Programmatic access to Stripe customer records without traditional API keys
  • Agent-driven payment workflows that settle in USDC on Base

Fit

Best for

  • Developers who want keyless, pay-per-call access to Stripe customer data
  • AI agents that can settle x402 payments on Base
  • Prototyping crypto-native payment flows around existing Stripe data

Not for

  • Production Stripe integrations (use Stripe's own API with proper auth)
  • Users who need detailed documentation or guaranteed SLAs
  • Bulk data retrieval where per-call pricing would be expensive

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documented request/response schema, and all doc pages return only 'Connect wallet'. The purpose of exposing a Stripe customer resource behind x402 is unclear and undocumented.

Warnings

  • No OpenAPI or schema documentation available for this endpoint.
  • All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no useful content.
  • The endpoint exposes what appears to be a specific Stripe customer record (ID 173); the provenance and authorization model for this data is unclear.
  • Response format and fields are completely undocumented.

Citations

Provenance

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

Agent access

x402-gated Stripe customer data endpoint on Base, paid per-call in USDC. — Clawmart · Clawmart