x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a Stripe customer resource (customer ID 90) behind an x402 paywall. 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 priced at $0.02 per request, settled in USDC on the Base network.
The specific endpoint `/api/v1/stripe/customers/90` is labeled "Premium API Access" by the provider. The x402 challenge confirms it is live, accepting POST requests, and requires a payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) per call. Payment is made via the x402 "exact" scheme to the provider's wallet. No API keys are required; authentication is handled entirely through the x402 payment header.
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 endpoint actually returns beyond its title. The platform's landing page lists many endpoints but provides no technical detail about request formats or response payloads. Users should expect to experiment or contact the provider for integration guidance.
Capabilities
Use cases
- —Retrieving Stripe customer data for customer ID 90 via a single paid API call
- —Integrating pay-per-request Stripe data access into agent workflows without API key management
- —Demonstrating x402 payment protocol usage for gated API access
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing one-off Stripe customer lookups without subscription overhead
- —Projects requiring keyless, pay-as-you-go API access on Base
Not for
- —High-volume Stripe data retrieval (no bulk or batch support evident)
- —Users who need detailed API documentation or guaranteed SLAs
- —Accessing arbitrary Stripe customer IDs (endpoint is hardcoded to customer 90)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/90 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"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 endpoint (Stripe customer 90) is unclear. The listing is effectively a stub.
Warnings
- —No documentation available — all doc/pricing/API pages render only 'Connect wallet'
- —No OpenAPI or request/response schema provided
- —Endpoint is hardcoded to a single Stripe customer ID (90); unclear what data is returned
- —Provider platform lists many endpoints but none have technical documentation
- —Purpose of exposing a single Stripe customer record via x402 is unclear
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/90
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/90