x402-gated Stripe customer data endpoint on Base, paid per-request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 190) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.
The specific endpoint `/api/v1/stripe/customers/190` is listed as "Premium API Access" and costs up to 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing across a wide catalog of endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities. All endpoints are x402-gated — no API keys, no rate limits, and no signup required. Payment is handled inline via the X-PAYMENT header on the Base L2 network.
Note that the crawled documentation pages (docs, api, pricing, README) all returned only a "Connect wallet" prompt with no substantive content, so details about the actual data returned by this specific Stripe customers endpoint are unknown. The endpoint is live and returning a valid 402 challenge, but without schema documentation or example responses, the exact shape and content of the response cannot be confirmed.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 190 via a single paid request
- —Programmatic access to payment/customer data without traditional API key management
- —Agent-driven workflows that need on-demand Stripe customer lookups settled in crypto
Fit
Best for
- —Agents or scripts that need one-off Stripe customer data without account setup
- —Developers exploring x402 payment flows on Base
- —Scenarios where pay-per-request is preferred over subscription billing
Not for
- —Bulk retrieval of many Stripe customers (single-resource endpoint, $0.02 each)
- —Users who need detailed API documentation or response schema guarantees before integrating
- —Non-crypto workflows that cannot send an X-PAYMENT header with USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/190 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI schema, no response examples, and all documentation pages are empty (just 'Connect wallet'). The purpose of a 'Stripe customers/190' endpoint is unclear — it could be a demo or placeholder. Effectively a stub listing.
Warnings
- —All documentation pages (docs, api, pricing, README) returned no content beyond 'Connect wallet'
- —No response schema or example response available — the actual data returned is unknown
- —The endpoint targets a specific customer ID (190), which may be a demo/test resource rather than a general-purpose API
- —The relationship between this endpoint and actual Stripe data is unclear; it may expose third-party customer data, raising privacy concerns
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/190
- —The platform advertises $0.02/request uniform 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/190