x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides x402-protocol access to a Stripe customer resource (customer ID 88). It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind x402 payment challenges settled in USDC on the Base network.
The specific endpoint `/api/v1/stripe/customers/88` is listed under the title "Premium API Access." The x402 challenge confirms it accepts POST requests, requires an exact payment of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals → $0.02), and returns application/json. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is purely payment-gated.
Documentation is extremely thin — 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 beyond the x402 outputSchema stub, and no explanation of what data the Stripe customers endpoint actually returns. The platform's landing page confirms uniform $0.02 pricing across all endpoints and lists categories (analytics, AI, finance, infrastructure), but provides no detailed documentation for any individual endpoint.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 88 via a single paid API call
- —Programmatic access to Stripe customer data without managing API keys
- —Agent-driven workflows that need on-demand Stripe customer lookups settled in crypto
Fit
Best for
- —Agents or services that need one-off Stripe customer data access without subscription commitments
- —Developers experimenting with x402 payment-gated APIs on Base
- —Workflows requiring keyless, pay-as-you-go API access
Not for
- —Bulk Stripe data retrieval — only a single customer ID (88) is exposed at this endpoint
- —Users who need detailed API documentation or request/response schemas before integrating
- —Anyone without USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/88 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is virtually no documentation: no OpenAPI spec, no request body schema, no response schema, and no explanation of what the Stripe customers/88 endpoint actually returns. The docs pages are empty wallet-connect stubs. The endpoint's purpose is unclear beyond its title.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all render only 'Connect wallet' with no content.
- —No request or response schema provided; it is unknown what data this endpoint returns or what POST body it expects.
- —The endpoint is scoped to a single Stripe customer ID (88); unclear if other customer IDs are available at different paths.
- —The platform lists many endpoint categories (AI, analytics, finance, etc.) but none have documented schemas or examples.
Citations
- —The x402 challenge requires 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network, equaling $0.02.https://lowpaymentfee.com/api/v1/stripe/customers/88
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.https://lowpaymentfee.com/api/v1/stripe/customers/88
- —Documentation pages (/docs, /pricing, /api, /README) render only a 'Connect wallet' prompt with no further content.https://lowpaymentfee.com/docs