x402basequality 0.30

x402-gated Stripe customer data endpoint on Base, paid per-request 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 107) 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 provider lowpaymentfee.com hosts a broader 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/107) is not listed on the provider's public catalog page and appears to expose Stripe customer data, which is unusual for a public pay-per-call API. The exact response payload is undocumented; no OpenAPI spec, example requests, or example responses are available.

The endpoint is confirmed live: it returns a valid x402 version-1 challenge with a 402 status code. Documentation pages (/docs, /pricing, /api, /README) all resolve but contain only a "Connect wallet" prompt with no substantive content. Because the endpoint's purpose and response schema are unclear — and because exposing Stripe customer records raises data-handling questions — users should exercise caution.

Capabilities

x402-paymentusdc-basestripe-customer-dataper-request-billingjson-response

Use cases

  • Retrieving Stripe customer information for customer ID 107 via a pay-per-call model
  • Programmatic access to customer billing data without managing API keys
  • Agent-driven workflows that need on-demand Stripe customer lookups

Fit

Best for

  • Developers needing one-off Stripe customer data access without Stripe API keys
  • AI agents that can settle x402 payments on Base in USDC
  • Workflows requiring keyless, per-request billing for customer data

Not for

  • Bulk retrieval of multiple Stripe customers (endpoint is scoped to a single customer ID)
  • Users who need detailed documentation or guaranteed SLAs
  • Applications requiring non-crypto payment methods

Quick start

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

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 no OpenAPI spec, no documented request/response schema, no example payloads, and the docs pages are empty. The endpoint's purpose (exposing a single Stripe customer record) is unusual and undocumented, raising data-handling concerns.

Warnings

  • No OpenAPI or schema documentation available; response format is unknown.
  • Endpoint exposes Stripe customer data — verify data-handling compliance and authorization before use.
  • This specific endpoint (/api/v1/stripe/customers/107) is not listed on the provider's public catalog page.
  • All documentation pages (/docs, /pricing, /api, /README) contain only a 'Connect wallet' prompt with no content.
  • Endpoint is scoped to a single hardcoded customer ID (107); unclear if other IDs are accessible.

Citations

Provenance

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

Agent access