x402basequality 0.35

x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 134) 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 endpoint charges a maximum of 20,000 base units of USDC per request. Since USDC uses 6 decimals, this equals $0.02 per call — consistent with the provider's site-wide flat pricing of $0.02/request. The provider advertises no API keys, no rate limits, and instant access; payment is the only authentication mechanism.

The broader lowpaymentfee.com platform hosts a variety of x402-gated APIs spanning data/analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). However, this specific listing is for the Stripe customers endpoint at `/api/v1/stripe/customers/134`. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so the exact request/response schema for this endpoint is unknown.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-dataper-call-pricingno-api-keyjson-response

Use cases

  • Retrieving Stripe customer details via a pay-per-call model without needing API keys
  • Agent-driven workflows that need on-demand access to Stripe customer records
  • Programmatic access to payment platform data settled in crypto

Fit

Best for

  • Developers who want keyless, pay-per-request access to Stripe customer data
  • AI agents that can settle x402 payments on Base in USDC
  • Prototyping integrations where traditional Stripe API key management is undesirable

Not for

  • Bulk retrieval of many Stripe customers (each call costs $0.02 and only targets one customer ID)
  • Users who need detailed API documentation or response schema guarantees before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/134 \
  -H "X-PAYMENT: <x402-payment-token>" \
  -H "Content-Type: application/json"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is no documentation, no request/response schema, and the purpose of exposing a single Stripe customer record behind a paywall is unclear. All doc pages returned only 'Connect wallet' with no content.

Warnings

  • No API documentation available — all doc pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no content.
  • The endpoint targets a single hardcoded Stripe customer ID (134); the use case and response format are unknown.
  • No OpenAPI spec, no request body schema, and no response schema are provided.
  • The nature of the data returned (whether it is real Stripe customer data or a demo) is unverifiable from available material.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 09:50:26Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-27

Agent access