x402-gated Stripe customer data endpoint on Base, paid per-request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 159) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.
The specific endpoint `/api/v1/stripe/customers/159` is listed as "Premium API Access" and costs up to $0.02 per request (maxAmountRequired of 20,000 base units of USDC, which has 6 decimals = $0.02). The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.
The endpoint is live and returning a valid x402 challenge (HTTP 402 with proper accepts array). However, 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 data this Stripe customer endpoint actually returns. The exact purpose of fetching a Stripe customer record via a paid proxy is unclear from available materials.
Capabilities
Use cases
- —Retrieving Stripe customer data for customer ID 159 via a pay-per-request model
- —Demonstrating x402 protocol payment flows on Base network
- —Agent-driven access to payment-gated resources without API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-per-call API access
- —Projects already operating on Base network with USDC
Not for
- —Production Stripe integrations requiring full customer CRUD operations
- —Users needing detailed API documentation or schema guarantees
- —Bulk data retrieval where per-request pricing is inefficient
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/159 \
-H "X-PAYMENT: <x402-payment-token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and the purpose of this specific Stripe customer endpoint is unclear. The listing is effectively a stub.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only a 'Connect wallet' prompt.
- —No OpenAPI or schema available; request body format and response structure are unknown.
- —The purpose of exposing a single Stripe customer record (ID 159) behind a paywall is unclear — this may be a demo or test endpoint.
- —No response examples available to verify what data is actually returned.
Citations
- —Endpoint returns HTTP 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/159
- —maxAmountRequired is 20000 base units of USDC (USD Coin, 6 decimals = $0.02)https://lowpaymentfee.com/api/v1/stripe/customers/159
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/159