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/139`) behind an x402 paywall. The provider operates a broader platform offering dozens of pay-per-call API endpoints across categories like data analytics, AI/ML inference, finance, and utilities — all settled in USDC on the Base network via the x402 protocol. The specific endpoint probed here appears to return Stripe customer data for customer ID 139.
Pricing for this endpoint is $0.02 per request (the x402 challenge advertises a maxAmountRequired of 20000 base units of USDC on Base, which equals $0.02 given USDC's 6 decimals). Payment is made inline via the X-PAYMENT header — no API keys, accounts, or rate limits are required. The endpoint accepts POST requests and returns application/json.
Documentation is extremely sparse. The provider's docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the endpoint actually returns. The broader site lists many endpoints but provides no detail on input parameters or response formats for any of them.
Capabilities
Use cases
- —Retrieving Stripe customer information without needing a Stripe API key or account
- —Agent-driven lookups of customer records with inline micropayments
- —Programmatic access to payment platform customer data via crypto settlement
Fit
Best for
- —Agents that need on-demand Stripe customer data without subscription overhead
- —Developers experimenting with x402 payment flows on Base
- —Low-volume, pay-as-you-go access to customer records
Not for
- —High-volume Stripe integrations (direct Stripe API would be cheaper and better documented)
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Anyone needing bulk customer data export
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/139 \
-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/request in USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages all render only a wallet-connect prompt. The endpoint's actual functionality (returning Stripe customer data) is inferred solely from the URL path. This is effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No OpenAPI or schema definition for request or response payloads
- —Endpoint purpose inferred solely from URL path (/api/v1/stripe/customers/139); actual response content is unknown
- —Exposing Stripe customer data via a public pay-per-call endpoint raises data privacy and compliance concerns
- —No information on data freshness, accuracy, or source authorization
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/139
- —The provider lists endpoints at $0.02/request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompt with no substantive documentationhttps://lowpaymentfee.com/docs