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/65`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call API endpoints across data analytics, AI/ML inference, finance, and utility categories, all settled on the Base network using USDC. The specific endpoint listed here appears to return Stripe customer data for customer ID 65.
The x402 challenge confirms the endpoint is live and accepts payment via the "exact" scheme on Base mainnet. The maximum amount required is 20,000 base units of USDC (contract `0x8335…2913`), which at 6 decimals equals $0.02 per request — consistent with the provider's advertised flat pricing of $0.02/request across all endpoints. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a 300-second timeout. The response MIME type is `application/json`.
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 endpoint returns. The endpoint's purpose — exposing Stripe customer records via a crypto paywall — is unusual and raises questions about data provenance and authorization. Prospective callers should verify the legitimacy and data-privacy compliance of this endpoint before use.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 65 via a single paid API call
- —Demonstrating x402 payment protocol integration with a live endpoint
- —Programmatic access to customer records without traditional API key authentication
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that can settle USDC payments on Base network
- —Use cases requiring keyless, pay-per-call API access
Not for
- —Production systems needing documented, stable API contracts
- —Bulk retrieval of multiple customer records
- —Users who need clear data-privacy and compliance guarantees
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/65 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02/call in USDC on Base). However, there is no documentation, no request/response schema, no examples, and the purpose of exposing a specific Stripe customer record behind a crypto paywall is unexplained and potentially concerning from a data-privacy standpoint.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
- —No request or response schema provided; callers cannot know what fields are returned.
- —Endpoint exposes Stripe customer data — data provenance, authorization, and privacy compliance are unclear.
- —Only a single hardcoded customer ID (65) is in the URL; unclear if other IDs are supported or what the broader use case is.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/65
- —The provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/65