x402-gated Stripe customer endpoint on Base, pay-per-call with USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/125`) behind an x402 payment wall. It accepts POST requests and requires an X-PAYMENT header carrying a Base-network USDC payment. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 USD per request.
The parent site lowpaymentfee.com advertises a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here (`/stripe/customers/125`) does not appear in the site's public catalog and its exact functionality is unclear. The description simply says "Premium API Access" with no further documentation on request/response schemas.
The endpoint is confirmed live: the probe received a proper HTTP 402 challenge with x402 version 1, settling on Base via USDC (contract `0x8335…2913`). Payment is sent to address `0x1A2B…85F3` with a 300-second timeout. No OpenAPI spec, detailed docs, or example responses were found — the docs, pricing, API, and README pages all returned only a "Connect wallet" prompt with no substantive content.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model
- —Programmatic access to customer billing data without traditional API key management
- —Agent-driven payment workflows that settle in USDC on Base
Fit
Best for
- —Developers wanting keyless, pay-per-call access to Stripe customer data
- —AI agents that can settle x402 payments on Base
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Anyone needing detailed API documentation or response schema guarantees before integrating
- —Bulk retrieval of many Stripe customers (no batch endpoint documented)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/125 \
-H "X-PAYMENT: <x402-payment-token>" \
-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, no examples, and the docs pages are empty. The specific endpoint (/stripe/customers/125) is not listed in the site's public catalog, making its purpose and output unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /stripe/customers/125 path is not listed in the site's public API catalog — its exact purpose is undocumented
- —All documentation pages (docs, pricing, API, README) returned only 'Connect wallet' with no content
- —Request and response body formats are completely unknown — integration requires trial and error
- —The endpoint references a specific Stripe customer ID (125), which may indicate it returns third-party billing data; exercise caution regarding data sensitivity
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/125
- —The site advertises all APIs at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/125