x402-gated Stripe customer data endpoint on Base, paid per-request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a specific Stripe customer resource (`/api/v1/stripe/customers/161`) behind an x402 paywall. It 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 at 6 decimals equals $0.02 USD per request.
The broader lowpaymentfee.com platform advertises a catalog of pay-per-call APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no commitments required. However, the specific endpoint being listed here is under the Stripe customers path, which is not documented on the site's public landing page. Its exact response payload is unknown — no OpenAPI schema, output examples, or detailed documentation were found.
Because the endpoint path references a Stripe customer record by ID, it likely returns customer metadata from Stripe's billing system. The lack of documentation for this specific route, combined with the absence of any output schema beyond the x402 challenge, means agents should treat this as a partially documented endpoint. The x402 challenge was successfully captured (HTTP 402), confirming the endpoint is live.
Capabilities
Use cases
- —Retrieving Stripe customer metadata via a pay-per-request model
- —Programmatic access to billing customer records without API key management
- —Agent-driven lookups of customer data settled in USDC on Base
Fit
Best for
- —Agents needing on-demand Stripe customer data without subscription overhead
- —Developers experimenting with x402 payment flows on Base
- —Scenarios requiring keyless, per-call API access
Not for
- —Bulk retrieval of many Stripe customers (no batch endpoint documented)
- —Use cases requiring detailed output schema guarantees before calling
- —Users who need non-crypto payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/161 \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is no OpenAPI spec, no documented output schema, no example responses, and the specific /stripe/customers/161 path is not mentioned anywhere in the site's public documentation. This is effectively a stub listing with verified liveness.
Warnings
- —The /api/v1/stripe/customers/161 path is not listed on the provider's public landing page — only generic API categories are shown.
- —No output schema or example response is available; the actual response payload is unknown.
- —Docs, pricing, API, and README pages all returned only 'Connect wallet' with no substantive content.
- —Exposing Stripe customer data via a public pay-per-call endpoint may raise data privacy concerns.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/stripe/customers/161
- —All listed endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/stripe/customers/161