x402-gated Stripe customer endpoint on Base, paying $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a Stripe customer resource (`/api/v1/stripe/customers/83`) behind an x402 payment challenge. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 protocol on the Base network.
The specific endpoint listed here accepts POST requests and returns JSON. Payment is settled in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) with a maximum amount of 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). The x402 challenge was successfully captured, confirming the endpoint is live. No API keys or rate limits are advertised; access is granted purely through per-request micropayment.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the Stripe customers endpoint actually returns or what input it expects. The platform's landing page lists many endpoints at $0.02 each but provides no detail on request formats or response payloads. The exact purpose of accessing a Stripe customer record (ID 83) via a paid proxy is unclear.
Capabilities
Use cases
- —Retrieving Stripe customer data without managing API keys
- —Agent-driven per-request access to financial records
- —Programmatic micropayment-gated data retrieval
Fit
Best for
- —Agents that need one-off Stripe customer lookups via micropayment
- —Developers exploring x402 payment protocol integrations
- —Use cases where keyless, pay-per-call access is preferred
Not for
- —Production Stripe integrations requiring full API coverage and documentation
- —High-volume batch processing where per-request fees add up
- —Users who need detailed API documentation before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/83 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty beyond a wallet connect prompt. The purpose of exposing a specific Stripe customer record (ID 83) is unexplained, making this effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages are all empty
- —No OpenAPI or request/response schema provided
- —The purpose of exposing a single Stripe customer record (ID 83) is unclear and potentially sensitive
- —No information on what POST body the endpoint expects or what it returns
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/83
- —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/83