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 168) 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 maximum amount required per call is 20,000 base units of USDC, which equals $0.02 USD (USDC uses 6 decimals).
The hosting provider, lowpaymentfee.com, advertises a broad 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. However, this specific endpoint (/api/v1/stripe/customers/168) is not listed among the publicly advertised APIs on the landing page. Its path suggests it returns Stripe customer data for a particular customer record, but no documentation, request schema, or response schema is available beyond the x402 challenge metadata.
Because the crawled docs, pricing, API, and README pages all returned only a "Connect wallet" prompt with no substantive content, the actual behavior, input parameters, and response format of this endpoint remain unknown. The endpoint is confirmed live (returns a valid x402 402 challenge), but prospective callers should be aware that there is no published documentation describing what data is returned or what POST body (if any) is expected.
Capabilities
Use cases
- —Retrieving Stripe customer details for customer ID 168 via a pay-per-request model
- —Programmatic access to customer billing data without traditional API key management
- —Agent-driven workflows that need on-demand Stripe customer lookups settled in crypto
Fit
Best for
- —Developers or agents needing one-off Stripe customer data access without subscription commitments
- —x402-compatible agents that can settle USDC payments on Base
- —Workflows requiring keyless, pay-as-you-go API access
Not for
- —Bulk retrieval of many Stripe customers (only a single customer ID is exposed)
- —Users who need detailed documentation or guaranteed SLAs before calling
- —Non-crypto users who cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/168 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and no explanation of what data is actually returned. The specific resource path (/stripe/customers/168) is not listed among the provider's advertised APIs, raising questions about its intended use. Effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, API, and README pages all return only a wallet-connect prompt with no content.
- —This specific endpoint (/api/v1/stripe/customers/168) is not listed among the provider's publicly advertised APIs.
- —No request body schema or response schema is published; callers cannot know what to send or what to expect back.
- —The endpoint appears to expose a single hardcoded Stripe customer ID (168), which limits general utility.
- —Potential privacy concern: endpoint may expose third-party Stripe customer data without clear authorization context.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Base network.https://lowpaymentfee.com/api/v1/stripe/customers/168
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/stripe/customers/168
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The provider lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories, but this specific endpoint is not among them.https://lowpaymentfee.com