Stripe customer data endpoint on Base via x402, pay $0.02 per request in USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com provides access to Stripe customer data (specifically customer ID 171) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a per-call cost of $0.02 (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 endpoint is part of a broader platform (lowpaymentfee.com) that advertises multiple API categories including data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. However, this specific listing covers only the `/api/v1/stripe/customers/171` route, which appears to return Stripe customer information in JSON format. The exact response schema is not documented in the crawled material.
The platform emphasizes simplicity: no subscriptions, no minimums, no commitments. The x402 challenge was successfully captured with version 1, confirming the endpoint is live. Documentation pages (/docs, /pricing, /README) returned only a "Connect wallet" prompt with no substantive content, so the actual request/response contract for this endpoint remains unclear.
Capabilities
Use cases
- —Retrieving Stripe customer details without managing API keys or subscriptions
- —Agent-driven payment workflows that settle per-call in USDC on Base
- —Programmatic access to customer records with crypto-native micropayments
Fit
Best for
- —Developers wanting keyless, pay-per-use access to Stripe customer data
- —AI agents that can settle x402 payments autonomously on Base
- —Prototyping integrations where traditional Stripe API key management is undesirable
Not for
- —Bulk retrieval of many Stripe customers (single customer ID hardcoded in URL)
- —Users who need detailed API documentation or response schema guarantees
- —Production systems requiring SLA guarantees or support
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/171 \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no documented request body schema, no response schema, and all documentation pages returned only a wallet-connect prompt. The endpoint path suggests a single hardcoded Stripe customer ID (171), which limits utility. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, and /README pages all returned only 'Connect wallet' with no content.
- —The endpoint path includes a hardcoded customer ID (171); it is unclear whether other customer IDs are accessible or what data is returned.
- —Response schema is completely undocumented; callers cannot predict the shape of a successful response.
- —The purpose and legitimacy of exposing Stripe customer data via a public pay-per-call endpoint is unclear — potential data privacy concerns.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base at 20000 base unitshttps://lowpaymentfee.com/api/v1/stripe/customers/171
- —Platform advertises $0.02 per request, no API keys, no rate limits, no minimumshttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/171
- —Documentation pages (/docs, /pricing, /README) returned only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs