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 49). It is part of a broader platform offering pay-per-request APIs across data analytics, AI/ML inference, finance, and utility categories — all gated behind x402 payment challenges settled in USDC on the Base network at $0.02 per call.
The specific endpoint `/api/v1/stripe/customers/49` is labeled "Premium API Access" and accepts POST requests. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no description of what data the Stripe customer endpoint actually returns. The platform lists many other endpoints (analytics, AI, finance, utilities) at the same $0.02 price point, but none have documented schemas or example payloads. Prospective callers should be aware that the actual response format is unknown and must be discovered empirically.
Capabilities
Use cases
- —Retrieving Stripe customer details for customer ID 49 via a single paid request
- —Integrating pay-per-call Stripe data access into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base with USDC
Fit
Best for
- —Agents or developers needing keyless, pay-per-request access to Stripe customer data
- —Experimenting with x402 protocol payment flows on Base
- —Low-volume, on-demand lookups where subscription billing is overkill
Not for
- —High-volume Stripe integrations where direct Stripe API access is cheaper and better documented
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Accessing arbitrary Stripe customers — this endpoint is scoped to customer ID 49
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/49 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) 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 the purpose of a 'Stripe customers/49' endpoint is unexplained. This is effectively a stub listing.
Warnings
- —No OpenAPI spec or request/response schema available — actual payload format is unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
- —The endpoint is scoped to a single Stripe customer ID (49); unclear if this is a demo or production resource
- —No information on what data is returned or what POST body is expected
- —The platform lists many endpoints but none appear to have documented behavior
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base with a 300-second timeouthttps://lowpaymentfee.com/api/v1/stripe/customers/49
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —USDC contract address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/49
- —Documentation pages /docs, /api, /pricing, /README all show only 'Connect wallet'https://lowpaymentfee.com/docs