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 149) 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 hosting site lowpaymentfee.com advertises a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the x402 challenge for this specific endpoint advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site's stated pricing.
Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no explanation of what the Stripe customers endpoint actually returns or what input it expects. The endpoint is confirmed live (402 challenge captured), but the actual functionality and data returned remain unclear.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model without API key management
- —Programmatic access to customer records settled in USDC on Base
- —Agent-driven workflows that need on-demand Stripe customer data with crypto payment
Fit
Best for
- —Developers wanting keyless, pay-per-request access to Stripe customer data
- —AI agents that can settle x402 payments in USDC on Base
- —Prototyping integrations where traditional Stripe API key provisioning is undesirable
Not for
- —Production systems needing documented request/response schemas and SLAs
- —Bulk retrieval of many Stripe customers (single-resource endpoint, $0.02 per call)
- —Users who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/149 \
-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 USDC on Base), but there is no documentation, no OpenAPI spec, no request/response examples, and no explanation of what data is actually returned. The docs pages are all empty wallet-connect stubs. Effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all return only a wallet connect prompt
- —No OpenAPI or request/response schema provided; actual endpoint behavior is unknown
- —Purpose of exposing a single Stripe customer record (ID 149) via public paywall is unclear
- —No information on data freshness, uptime guarantees, or rate limits beyond marketing claims
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/stripe/customers/149
- —The site 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/149