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 21) via a POST request. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind x402 payment challenges settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/customers/21` is labeled "Premium API Access" by the provider. The x402 challenge advertises a maximum amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 USD (USDC uses 6 decimals). Payment is made via the `exact` scheme to the provider's wallet. No API keys are required; authentication is handled entirely through the x402 payment header. The provider claims 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 substantive content. There is no OpenAPI schema, no request/response examples, and no description of what data this endpoint actually returns. The endpoint is confirmed live (returns a proper 402 challenge), but the actual functionality behind the paywall is unclear from available materials.

Capabilities

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

Use cases

  • Retrieving Stripe customer data for customer ID 21 via a paid API call
  • Demonstrating x402 payment protocol integration with USDC on Base
  • Agent-driven programmatic access to premium data without API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that can settle USDC payments on Base network
  • Use cases requiring keyless, pay-per-call API access

Not for

  • Users needing well-documented APIs with clear request/response schemas
  • Bulk data retrieval where per-request pricing would be costly
  • Anyone without a Base-network USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/21 \
  -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 documentation is essentially nonexistent — every doc page shows only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. The purpose of a 'Stripe customers/21' endpoint on a generic paid-API platform is unclear.

Warnings

  • Documentation pages (docs, API, pricing, README) contain no useful content — only 'Connect wallet' prompts.
  • No OpenAPI or schema available; request body format and response structure are completely unknown.
  • The specific purpose of accessing Stripe customer ID 21 through a third-party pay-per-call API is unclear and potentially suspicious.
  • No information about data freshness, accuracy, or underlying data sources.

Citations

Provenance

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

Agent access