Stripe customer data endpoint paid per-request via x402 on Base (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to Stripe customer data (specifically the `/api/v1/stripe/customers/200` resource) behind an x402 paywall. The provider operates a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all settled on the Base network using USDC.
The specific endpoint probed returns an x402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per call, consistent with the site-wide advertised price of $0.02 per request. Payment is made via the x402 "exact" scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The endpoint accepts POST requests and returns `application/json`.
Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no explanation of what the Stripe customers endpoint actually returns or what input it expects. The endpoint path suggests it retrieves or interacts with Stripe customer records (the trailing `/200` may be a customer ID or limit parameter), but this is speculative. The provider advertises no API keys, no rate limits, and instant access across all endpoints.
Capabilities
Use cases
- —Retrieving Stripe customer information without maintaining a Stripe API key directly
- —Agent-driven access to customer records with per-call crypto payment
- —Programmatic lookup of Stripe customer data settled via USDC on Base
Fit
Best for
- —Agents needing on-demand Stripe customer data without subscription commitments
- —Developers wanting crypto-settled API access to payment platform data
- —Low-volume or sporadic access to Stripe customer records at $0.02/call
Not for
- —High-volume Stripe integrations where a direct Stripe API key is more cost-effective
- —Use cases requiring detailed documentation or guaranteed SLAs
- —Applications needing non-USDC or non-Base-network payment options
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/200 \
-H "X-PAYMENT: <x402-payment-header>" \
-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 — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the endpoint does beyond its URL path. The purpose of a 'Stripe customers' endpoint behind a crypto paywall is unclear and potentially unusual.
Warnings
- —Documentation pages (docs, pricing, API, README) all render only 'Connect wallet' with no usable content
- —No OpenAPI or request/response schema available — input format and response structure are unknown
- —The purpose of proxying Stripe customer data behind an x402 paywall is unclear; verify the endpoint actually returns useful data before relying on it
- —No information on data freshness, accuracy, or what Stripe account the data originates from
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC ($0.02) on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/200
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/200
- —Docs, pricing, API, and README pages render only 'Connect wallet'https://lowpaymentfee.com/docs