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/198`) 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 probed (`/api/v1/stripe/customers/198`) is described as "Premium API Access" and accepts POST requests. It returns JSON and costs up to 20,000 base units of USDC (0.02 USD) per request. Payment is made by attaching an X-PAYMENT header with a signed x402 payment voucher. The asset used is USDC on Base (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), with a 300-second payment timeout.
Documentation is extremely sparse—the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional content. There is no OpenAPI spec, no request/response schema, and no explanation of what data this endpoint actually returns or what POST body it expects. The endpoint is live (returns a valid 402 challenge), but without documentation it is difficult to determine the practical utility of this specific resource. The broader site advertises a uniform $0.02/request pricing model with no API keys, no rate limits, and instant access.
Capabilities
Use cases
- —Retrieving Stripe customer data via a pay-per-call model without needing API keys
- —Programmatic access to premium data endpoints settled in USDC on Base
- —Agent-driven workflows that need on-demand paid API access without subscriptions
Fit
Best for
- —Developers or agents who want keyless, pay-per-call API access
- —Users comfortable with x402 crypto payment flows on Base
- —Scenarios requiring one-off data retrieval without subscription commitments
Not for
- —Users who need detailed API documentation or request/response schemas before integrating
- —High-volume use cases where per-call pricing may add up compared to subscription plans
- —Anyone who cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/198 \
-H "X-PAYMENT: <x402-signed-payment-voucher>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no clarity on what data this endpoint actually returns. The listing is effectively a stub.
Warnings
- —No API documentation available—docs, pricing, API, and README pages all show only 'Connect wallet'
- —No request body schema or response schema provided; unclear what POST body is expected
- —No OpenAPI or ai-plugin manifest discovered
- —The specific endpoint path (/api/v1/stripe/customers/198) references a hardcoded customer ID with no explanation of its purpose
- —Cannot verify what data is actually returned without making a paid request
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/198
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/198
- —The site lists APIs across data analytics, AI/ML, finance/crypto, and infrastructure categorieshttps://lowpaymentfee.com