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/162`) behind an x402 paywall. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 0.02 USDC per request (20,000 base units at 6 decimals). No API keys or rate limits are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services — all priced at $0.02 per request. However, this specific listing is for the Stripe customers endpoint, which appears to return Stripe customer data for customer ID 162. The exact response schema is not documented in the crawled material.
Documentation on the site is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no example request/response payloads, and no description of what fields the Stripe customer endpoint returns. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to assess the actual utility or data returned.
Capabilities
Use cases
- —Retrieving Stripe customer details for customer ID 162 via a crypto-paid endpoint
- —Demonstrating x402 payment protocol integration with a live endpoint
- —Programmatic access to Stripe customer data without traditional API key management
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing pay-per-call access to Stripe customer data on Base
- —Projects that want to avoid API key provisioning overhead
Not for
- —Production Stripe integrations requiring full CRUD on arbitrary customer IDs
- —Users who need detailed API documentation or response schema guarantees
- —High-volume batch retrieval of Stripe data
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/162 \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The endpoint targets a single hardcoded Stripe customer ID with no explanation of what data is returned, making practical utility unclear.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README all show only a wallet-connect prompt
- —Response schema is completely undocumented; unknown what fields are returned
- —Endpoint is scoped to a single customer ID (162) with no indication of how to access other resources
- —Stripe customer data may contain PII — regulatory and privacy implications are unclear
Citations
- —Endpoint returns 402 with x402 challenge advertising USDC on Base network at maxAmountRequired 20000https://lowpaymentfee.com/api/v1/stripe/customers/162
- —Platform advertises $0.02 per request pricing 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/162