x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 133) behind an x402 payment wall. 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 maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). No API keys or rate limits are advertised; access is granted purely through the x402 payment header.
The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance/crypto market data, and utility services — all priced at $0.02 per request on the Base network. However, this specific listing covers only the `/api/v1/stripe/customers/133` endpoint, which appears to expose Stripe customer data. The exact fields returned are not documented; no OpenAPI schema, example responses, or detailed docs were found during crawling (docs, pricing, and README pages all returned only a "Connect wallet" prompt with no further content).
Because the endpoint's actual response payload and input parameters are undocumented, agents should treat this as a lightly-documented resource. The x402 challenge is live and well-formed, confirming the endpoint is operational.
Capabilities
Use cases
- —Retrieving Stripe customer information for customer ID 133 via a single paid API call
- —Demonstrating x402 payment-gated API access on the Base network
- —Integrating pay-per-call Stripe data retrieval into agent workflows
Fit
Best for
- —Agents needing on-demand Stripe customer data without managing API keys
- —Developers experimenting with x402 micropayment protocols
- —Automated workflows that need low-friction, per-call billing
Not for
- —Bulk retrieval of many Stripe customers (only one customer ID is exposed)
- —Use cases requiring detailed API documentation or guaranteed SLAs
- —Users who need free or subscription-based access
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/133 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works. However, there is no OpenAPI schema, no example request/response, and the docs/pricing/README pages are empty beyond a wallet-connect prompt. The endpoint exposes a single hardcoded Stripe customer ID with no documented input or output fields, making it essentially a stub listing.
Warnings
- —No API documentation found — docs, pricing, and README pages returned only 'Connect wallet' with no content.
- —Endpoint targets a single hardcoded Stripe customer ID (133); unclear what data is returned or whether other customer IDs are accessible.
- —No OpenAPI or output schema available; response format is unknown.
- —Exposing Stripe customer data may involve PII — verify compliance with data protection regulations before use.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/133
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/stripe/customers/133
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Docs, pricing, and README pages show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs