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 194) 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/194) 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 there is no documentation, schema, or example response available to confirm what the response payload contains.

Because the endpoint is live (returning a valid 402 challenge) but lacks any documentation beyond the generic "Premium API Access" label, the actual utility and response format remain unclear. Users should treat this as an opaque endpoint until further documentation is provided.

Capabilities

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

Use cases

  • Retrieving Stripe customer details for customer ID 194 via a pay-per-call model
  • Programmatic access to customer records without traditional API key management
  • Agent-driven payment flows using x402 on Base L2

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents that need on-demand access to specific Stripe customer records
  • Use cases where keyless, per-request billing is preferred

Not for

  • Bulk retrieval of multiple Stripe customers — this endpoint targets a single customer ID
  • Users who need documented response schemas before integrating
  • Anyone needing free or subscription-based access

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/194 \
  -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 402 challenge, but there is no documentation, no OpenAPI schema, no example responses, and the endpoint path (a specific Stripe customer ID) is not listed among the provider's advertised APIs. The actual response content is entirely unknown.

Warnings

  • This specific endpoint (/api/v1/stripe/customers/194) is not listed among the provider's publicly advertised APIs — its purpose and response format are undocumented.
  • No OpenAPI spec, response schema, or example payloads are available.
  • The docs, pricing, API, and README pages all render only a 'Connect wallet' prompt with no substantive content.
  • Accessing another party's Stripe customer data via a third-party pay-per-call endpoint raises data provenance and privacy concerns.

Citations

Provenance

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

Agent access

x402-gated Stripe customer data endpoint on Base, paid per-request in USDC. — Clawmart · Clawmart