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/121`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-request 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 returns JSON data related to Stripe customer ID 121. The x402 challenge confirms it accepts POST requests and charges up to 20,000 base units of USDC (0.02 USD) per call, settled on Base to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The asset contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` is the canonical USDC contract on Base. No API keys or rate limits are advertised; access is gated purely by the x402 payment header.
Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI schema, no request/response examples, and no description of what fields the Stripe customer endpoint actually returns. The endpoint is live (402 challenge confirmed), but the lack of documentation makes it difficult to know what data to send or expect back.
Capabilities
Use cases
- —Retrieving Stripe customer details via a single paid API call
- —Programmatic access to customer payment data without managing Stripe API keys directly
- —Agent-driven lookups of customer records settled in USDC on Base
Fit
Best for
- —Agents or services needing on-demand Stripe customer data without subscription overhead
- —Developers experimenting with x402 payment-gated APIs
- —Low-volume, pay-as-you-go access to customer records
Not for
- —High-volume Stripe integrations where direct Stripe API access is cheaper
- —Use cases requiring detailed documentation or guaranteed SLAs
- —Users who need non-USDC or non-Base settlement options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/121 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live with a valid x402 402 challenge, but documentation is effectively nonexistent — every doc/pricing/API page shows only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no explanation of what the Stripe customer endpoint returns or what input it expects. The listing is essentially a stub.
Warnings
- —Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no usable content.
- —No OpenAPI or schema available — request body and response format are completely unknown.
- —The endpoint path references a specific Stripe customer ID (121); unclear if this is a demo or production resource.
- —No information on what data is returned or what POST body is expected.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/121
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/121
- —The platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The provider offers endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com