x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 193) behind an x402 paywall. The endpoint 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 USD (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 only. Documentation pages (/docs, /pricing, /README) returned minimal content (just a "Connect wallet" prompt), so there is no detailed schema or field-level documentation available for request or response payloads.
The endpoint is live: the probe received a proper HTTP 402 with a well-formed x402 challenge. The x402 version is 1, the payment timeout is 300 seconds, and the payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. Without further documentation, the exact request body format and response schema remain unknown.
Capabilities
Use cases
- —Retrieving Stripe customer details for customer ID 193 via a single paid API call
- —Integrating pay-per-use Stripe data access into agent workflows without managing API keys
- —Programmatic access to payment platform customer records settled on-chain
Fit
Best for
- —Agents needing on-demand Stripe customer data without subscription commitments
- —Developers experimenting with x402 protocol payments on Base
- —Workflows requiring keyless, per-call API access to financial data
Not for
- —Bulk retrieval of many Stripe customers (single-resource endpoint, $0.02 each)
- —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/193 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation for request/response schemas, no OpenAPI spec, and the docs/pricing/README pages are effectively empty. The purpose of a 'Stripe customers/193' endpoint behind a public paywall is unclear and potentially a demo or placeholder.
Warnings
- —No request or response schema documentation available — all doc pages return only 'Connect wallet'
- —Endpoint targets a specific customer ID (193); unclear if this is a demo resource or production data
- —No OpenAPI or machine-readable schema provided
- —The nature of the data returned is unknown — could be synthetic/demo data
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/193
- —Platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/193