x402-gated Stripe customer endpoint on Base, paying $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a Stripe customer resource (`/api/v1/stripe/customers/94`) behind an x402 payment wall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required; callers simply attach an x402 payment header to each request.
The specific endpoint probed (`/api/v1/stripe/customers/94`) is labeled "Premium API Access" and accepts POST requests. The x402 challenge confirms it is live, requesting up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation is extremely sparse — the docs, API, pricing, 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 data this particular Stripe customer endpoint returns or what POST body it expects. The landing page lists many other endpoints but does not describe this one specifically. Prospective callers should treat this as a minimally documented endpoint and test carefully before relying on it in production.
Capabilities
Use cases
- —Retrieving Stripe customer information via a single paid POST request
- —Agent-driven workflows that need on-demand access to payment/customer data without API key management
- —Programmatic access to Stripe customer records settled with USDC on Base
Fit
Best for
- —Developers who want keyless, pay-per-use API access settled in crypto
- —AI agents that can attach x402 payment headers automatically
- —Low-volume or bursty workloads where subscription pricing is wasteful
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —High-volume Stripe integrations better served by Stripe's own API with bulk pricing
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/94 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no explanation of what the Stripe customer endpoint actually returns. This is effectively a stub listing.
Warnings
- —No OpenAPI or schema available — request body and response format are completely unknown.
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no usable content.
- —The endpoint path references a specific Stripe customer ID (94); it is unclear whether this is a demo, a real customer record, or a proxy.
- —No information on data freshness, uptime guarantees, or error handling.
Citations
- —The endpoint returns a 402 x402 challenge requesting up to 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).https://lowpaymentfee.com/api/v1/stripe/customers/94
- —The provider advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —Documentation, API, pricing, and README pages all show only a 'Connect wallet' prompt.https://lowpaymentfee.com/docs