x402-gated Stripe customer data endpoint on Base, paid per-request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 136) behind an x402 paywall. It 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. This particular endpoint's x402 challenge specifies a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 USD, consistent with the site's advertised pricing.
Documentation is extremely thin: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples. The endpoint path suggests it returns Stripe customer data for a hardcoded customer ID, but the exact request body format and response structure are unknown. The endpoint is live and returns a valid x402 402 challenge.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model without needing an API key
- —Programmatic access to customer records settled in USDC on Base
- —Agent-driven workflows that need on-demand Stripe data with crypto payment
Fit
Best for
- —Developers wanting keyless, pay-per-use access to Stripe customer data
- —AI agents that can settle x402 payments on Base in USDC
- —Prototyping integrations where traditional Stripe API key management is undesirable
Not for
- —Production systems needing documented request/response schemas and SLAs
- —Bulk retrieval of multiple Stripe customers (endpoint is scoped to a single customer ID)
- —Users who cannot pay in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/136 \
-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 documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages are empty. The purpose of the endpoint (Stripe customer data for a hardcoded ID) is unclear and niche. This is effectively a stub listing.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or request/response schema provided
- —Endpoint is scoped to a single hardcoded Stripe customer ID (136); unclear what data is returned or what POST body is expected
- —No information on data freshness, uptime guarantees, or rate limits beyond marketing claims
Citations
- —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
- —The x402 challenge specifies maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/136
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/136