x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/142`) 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 an X-PAYMENT header with a valid x402 payment proof.
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. However, this specific listing is for the Stripe customers endpoint, which appears to serve customer-record data. The exact response schema is not documented in the crawled material, so the precise fields returned are unknown.
The endpoint is live: the probe received a well-formed 402 challenge with x402 version 1. Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no example request/response, and no description of what the Stripe customer resource actually returns.
Capabilities
Use cases
- —Retrieving Stripe customer record data without managing API keys
- —Agent-driven workflows that need on-demand access to customer payment info
- —Programmatic access to Stripe customer details via crypto micropayment
Fit
Best for
- —Agents or bots that can settle USDC payments on Base
- —Developers wanting keyless, pay-per-call access to Stripe customer data
- —Workflows requiring low-friction API access without subscription commitments
Not for
- —Bulk retrieval of many Stripe customer records (no batch endpoint documented)
- —Users who need detailed API documentation or guaranteed SLAs
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/142 \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documented request/response schema, and the docs pages are empty stubs. The purpose of a 'Stripe customers/142' resource behind a crypto paywall is unclear and potentially suspicious. Effectively a stub listing.
Warnings
- —No OpenAPI spec or response schema available — exact response format is unknown.
- —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no content.
- —The endpoint exposes what appears to be a specific Stripe customer record (ID 142); the legitimacy and data-privacy implications of serving third-party Stripe customer data via a public paywall are unclear.
- —No examples of request body or response body found in any crawled material.
Citations
- —The endpoint returns a 402 challenge with x402 version 1, accepting USDC on Base with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/stripe/customers/142
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base.https://lowpaymentfee.com/api/v1/stripe/customers/142