x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/177`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC via the x402 protocol.
The specific endpoint listed here returns JSON data related to Stripe customer ID 177. The x402 challenge indicates a maximum cost of 20,000 base units of USDC (0.02 USD) per request, consistent with the provider's advertised flat $0.02/request pricing across all endpoints. Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base, with a 300-second timeout. No API keys or rate limits are advertised; access is gated entirely by the x402 payment header.
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 fields the Stripe customer resource actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data you'll receive or what POST body (if any) is expected.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 177 via a single paid API call
- —Programmatic access to customer data without managing API keys or subscriptions
- —Agent-driven workflows that need on-demand Stripe customer lookups settled in crypto
Fit
Best for
- —Developers or agents needing quick, keyless access to specific Stripe customer data
- —x402-compatible agents that can settle micropayments in USDC on Base
- —Use cases where per-call pricing is preferred over subscription billing
Not for
- —Bulk retrieval of many Stripe customers (only a single customer ID is exposed at this endpoint)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto workflows that cannot send x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/177 \
-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, but documentation is essentially nonexistent — every doc page shows only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no explanation of what the Stripe customer resource returns or what POST body is expected. The endpoint path suggests a single hardcoded customer ID, limiting general utility.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or response schema available — the shape of the returned data is unknown.
- —The endpoint targets a specific customer ID (177); it is unclear whether other customer IDs are available or how to discover them.
- —The purpose of exposing a Stripe customer record via a public paid API is unclear and may raise data privacy concerns.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (USD Coin, 6 decimals) on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/stripe/customers/177
- —The provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —Documentation, API, pricing, and README pages all render only a 'Connect wallet' prompt with no substantive content.https://lowpaymentfee.com/docs