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/192`) 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 accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 per request (USDC uses 6 decimals). The provider's landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required. Payment is made inline via the X-PAYMENT header per the x402 v1 specification.
Note that the exact data returned by this particular Stripe customers endpoint is not documented. The provider's docs, pricing, API, and README pages all render only a wallet-connect prompt with no additional technical documentation. There is no OpenAPI schema, no request/response examples, and no description of what fields the Stripe customer resource contains or what the POST body should look like. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to use without experimentation.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model without needing a Stripe account
- —Programmatic access to customer records settled in USDC on Base
- —Agent-driven workflows that need on-demand customer data with no subscription
Fit
Best for
- —Developers who want to pay per request with no API key or subscription
- —AI agents that can settle x402 payments on Base in USDC
- —Use cases requiring low-cost, on-demand access to Stripe customer data
Not for
- —Users who need detailed API documentation or request/response schemas before integrating
- —High-volume batch retrieval where per-call pricing becomes expensive
- —Anyone needing non-USDC or non-Base-network payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/192 \
-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/request in USDC on Base). However, there is no OpenAPI schema, no request/response documentation, and no examples. The docs/pricing/API pages are all empty wallet-connect screens. The purpose of a 'Stripe customers' endpoint behind a crypto paywall is unclear and undocumented.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all render only a wallet-connect prompt
- —No request body schema or response schema documented for this endpoint
- —The purpose of exposing a Stripe customer resource (ID 192) behind a public x402 paywall is unclear and may raise data privacy concerns
- —Cannot verify what data is actually returned without making a paid request
Citations
- —Flat $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —x402 challenge returns maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/192
- —Provider offers APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com