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 124) 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 specific endpoint `/api/v1/stripe/customers/124` is listed as "Premium API Access" and costs up to 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). This is consistent with the provider's site-wide pricing of $0.02 per request. The provider advertises no API keys, no rate limits, and instant access — payment is the only authentication mechanism.
The broader lowpaymentfee.com platform offers a range of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and utility services. All endpoints share the same $0.02/request pricing. However, this specific listing covers only the Stripe customers endpoint. Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what data the Stripe customer endpoint actually returns.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 124 via a pay-per-call model
- —Programmatic access to Stripe customer data without managing API keys
- —Agent-driven workflows that need on-demand Stripe customer lookups settled in USDC
Fit
Best for
- —Agents or services that need one-off Stripe customer data access without subscription commitments
- —Developers experimenting with x402 payment-gated APIs on Base
- —Workflows requiring crypto-native pay-per-use access to financial data
Not for
- —Bulk retrieval of many Stripe customers (only a single customer ID is exposed)
- —Users who need detailed API documentation or request/response schemas before integrating
- —Anyone without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/124 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no request/response examples, and documentation pages are empty stubs. The endpoint targets a single hardcoded Stripe customer ID (124), which is unusual and unexplained. The actual data returned is unknown.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only a 'Connect wallet' prompt.
- —No OpenAPI or request/response schema available; the shape of the response is entirely unknown.
- —The endpoint references a specific Stripe customer ID (124), which is unusual — unclear if this is a demo, a proxy, or real customer data.
- —No information on what POST body (if any) is expected.
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base network, maxAmountRequired 20000 base unitshttps://lowpaymentfee.com/api/v1/stripe/customers/124
- —Site-wide pricing is $0.02 per request 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/124