x402basequality 0.30

x402-gated Stripe customer endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides x402-protocol access to a Stripe customer resource (customer ID 72). It is part of a broader platform offering pay-per-call APIs across data analytics, AI/ML inference, finance, crypto, and utility categories — all priced at $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/customers/72` is labeled "Premium API Access" and accepts POST requests. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the USDC asset address on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) and a `maxAmountRequired` of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys are needed; authentication is replaced by per-request micropayment. The platform advertises no rate limits and instant access.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what data this particular endpoint returns beyond the generic "Premium API Access" label. The endpoint is live (402 challenge confirmed), but the actual functionality behind the paywall is unclear. The broader site lists many other endpoints (analytics, AI, finance, utilities) at the same price point, but none have documented schemas or example payloads.

Capabilities

x402-paymentusdc-micropaymentbase-networkstripe-customer-datapay-per-requestno-api-key

Use cases

  • Retrieving Stripe customer information via a single micropayment
  • Programmatic access to customer data without managing API keys
  • Agent-driven workflows that need on-demand Stripe customer lookups

Fit

Best for

  • Developers wanting keyless, pay-per-use access to Stripe customer data
  • AI agents that can settle x402 micropayments on Base
  • Prototyping integrations where traditional Stripe API key management is undesirable

Not for

  • Production Stripe integrations requiring full CRUD on customer objects — use Stripe's native API instead
  • Users who need detailed documentation or guaranteed SLAs before integrating
  • Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request parameters, response schema, or what 'Premium API Access' actually returns. Docs pages are empty beyond a wallet-connect prompt. Functionality behind the paywall is entirely opaque.

Warnings

  • No OpenAPI schema or request/response documentation available
  • Docs, API, pricing, and README pages all render only 'Connect wallet' with no content
  • The actual data returned by /api/v1/stripe/customers/72 is unknown — 'Premium API Access' is the only description
  • Cannot verify what Stripe customer data (if any) is actually served behind the paywall

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 10:05:41Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access