x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides premium API access to a Stripe customer resource via the x402 payment protocol. The specific path `/api/v1/stripe/customers/4` suggests it returns Stripe customer data for a given customer ID. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).
The provider's landing page advertises a broad suite of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request. No API keys or rate limits are required; access is instant via x402 payment headers on the Base network.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no usage examples available. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response payload structure for this Stripe customers endpoint is unknown.
Capabilities
Use cases
- —Retrieving Stripe customer details via a pay-per-request model without managing API keys
- —Integrating Stripe customer lookups into agent workflows that settle payments on Base in USDC
- —Accessing premium data endpoints with micropayments instead of subscription billing
Fit
Best for
- —Agents or services that need on-demand Stripe customer data without subscription overhead
- —Developers experimenting with x402 payment-gated APIs on Base
- —Low-volume consumers who prefer pay-per-call over monthly plans
Not for
- —High-volume Stripe integrations where direct Stripe API access would be cheaper
- —Use cases requiring detailed documentation, OpenAPI specs, or guaranteed SLAs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/4 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The actual functionality of the Stripe customers endpoint is only inferrable from the URL path. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — response format is unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no technical content
- —The specific behavior of /api/v1/stripe/customers/4 is unclear — it may return Stripe customer data or act as a proxy, but this is unverified
- —No request body schema is documented; POST method is indicated but required fields are unknown
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/4
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/4