x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/179`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC via the x402 protocol.
The specific endpoint listed here returns JSON data related to Stripe customer ID 179. The x402 challenge confirms it is live, accepts POST requests, and charges a maximum of 20,000 base units of USDC (0.02 USD) per call on the Base L2 network. The asset contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` is the canonical Base USDC contract. No API keys or rate limits are advertised; payment is the sole access control.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the Stripe customer endpoint actually returns beyond its title "Premium API Access." The exact purpose of exposing a Stripe customer record via a paid API is unclear and should be verified before use.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 179 via a single paid call
- —Programmatic access to customer payment data without managing Stripe API keys directly
- —Agent-driven workflows that need on-demand Stripe customer lookups
Fit
Best for
- —Agents or services needing one-off Stripe customer data retrieval
- —Developers experimenting with x402 payment-gated APIs
- —Use cases where avoiding Stripe API key management is desirable
Not for
- —Bulk Stripe customer data retrieval (single-customer endpoint only)
- —Users who need detailed documentation or schema guarantees before integration
- —Production systems requiring SLA or uptime commitments
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/179 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but documentation is effectively nonexistent — every doc page shows only 'Connect wallet.' There is no OpenAPI schema, no request/response examples, and the purpose of exposing a single Stripe customer record is unexplained. The listing is essentially a stub.
Warnings
- —No documentation available — all doc pages render only 'Connect wallet'
- —No OpenAPI or request/response schema provided
- —Purpose of exposing a specific Stripe customer record (ID 179) via paid API is unclear and potentially sensitive
- —No SLA, rate limit, or uptime guarantees documented
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/179
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/179
- —The platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —maxAmountRequired is 20000 base units (0.02 USDC with 6 decimals)https://lowpaymentfee.com/api/v1/stripe/customers/179