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/181`) 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 181. 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 an `X-PAYMENT` header using the x402 "exact" scheme, settling to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment timeout is 300 seconds.
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 explanation of what the Stripe customers endpoint actually returns or what parameters it accepts. The endpoint is live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what data to expect or how to structure a POST body.
Capabilities
Use cases
- —Retrieving Stripe customer information via a pay-per-call model without API key management
- —Programmatic access to customer payment data settled on-chain via USDC on Base
- —Agent-driven lookups of Stripe customer records with instant crypto-based billing
Fit
Best for
- —Developers wanting keyless, pay-as-you-go access to Stripe customer data
- —AI agents that can settle x402 payments on Base in USDC
- —Use cases requiring low-friction, per-request billing without subscriptions
Not for
- —Users needing detailed API documentation or response schema before integrating
- —High-volume Stripe data access where direct Stripe API integration would be cheaper
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/181 \
-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 this Stripe customers endpoint returns or accepts. The purpose of exposing a single Stripe customer record behind a paywall is unclear.
Warnings
- —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no content
- —No OpenAPI or request/response schema available — impossible to know expected input or output format
- —The purpose of a publicly-payable Stripe customer data endpoint is unclear and may raise data privacy concerns
- —This specific endpoint (/api/v1/stripe/customers/181) is not listed on the provider's homepage among their advertised APIs
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (USD Coin, 6 decimals = $0.02) on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/181
- —The provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com
- —Documentation, API, pricing, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs