x402basequality 0.25

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 143) 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 hosting site lowpaymentfee.com advertises a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here (/api/v1/stripe/customers/143) is not among the publicly documented APIs on the site's landing page. The x402 challenge for this endpoint advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site's stated flat pricing.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what data this Stripe customer endpoint actually returns. The endpoint is live (returns a valid 402 challenge), but the lack of documentation makes it difficult to know what to expect from a successful paid request.

Capabilities

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

Use cases

  • Retrieving Stripe customer information for customer ID 143 via a paid API call
  • Demonstrating x402 payment-gated API access on Base
  • Programmatic access to Stripe customer data without traditional API key management

Fit

Best for

  • Developers experimenting with x402 payment protocols
  • Agents that need on-demand Stripe customer lookups settled in USDC
  • Projects exploring pay-per-call API models without subscriptions

Not for

  • Production Stripe integrations requiring full CRUD on customer objects
  • Bulk retrieval of multiple Stripe customers
  • Users who need detailed API documentation before integrating

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, and no meaningful documentation beyond a wallet-connect prompt. The specific endpoint (/stripe/customers/143) is not listed among the site's advertised APIs, making its purpose unclear. This is effectively a stub listing.

Warnings

  • No OpenAPI or schema documentation available for this endpoint
  • The /docs, /pricing, /api, and /README pages contain no usable content — only a 'Connect wallet' prompt
  • This specific endpoint (/api/v1/stripe/customers/143) is not listed among the site's publicly advertised APIs
  • The endpoint appears to expose a single hardcoded Stripe customer ID (143) — unclear if this is a demo or production resource
  • No example request or response bodies are available; actual returned data is unknown

Citations

Provenance

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

Agent access