x402basequality 0.35

x402-gated Stripe customer data endpoint on Base, paid per-call 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 75) via the x402 payment protocol. It is part of a broader platform that offers dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated behind x402 micropayments settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/customers/75` is labeled "Premium API Access" and costs up to 20,000 base units of USDC (i.e., $0.02) per request. Payment is made inline via the X-PAYMENT header using the x402 "exact" scheme. The endpoint accepts POST requests and returns application/json. No API keys or accounts are required; access is granted purely through on-chain payment.

The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing model across all its endpoints, with no rate limits, no minimums, and no commitments. However, documentation beyond the landing page is essentially empty (all sub-pages just show "Connect wallet"), so the actual behavior, request schemas, and response formats for this and other endpoints are undocumented.

Capabilities

x402-paymentusdc-basestripe-customer-dataper-request-micropaymentno-api-keyjson-response

Use cases

  • Retrieving Stripe customer information for customer ID 75 via a single paid request
  • Demonstrating x402 micropayment integration for API access
  • Programmatic access to payment platform data without traditional API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol integrations
  • Agents that need to fetch Stripe customer data without managing API keys
  • Use cases requiring single-shot, no-commitment API calls settled on-chain

Not for

  • Bulk retrieval of multiple Stripe customers (endpoint is scoped to a single customer ID)
  • Users who need detailed API documentation or request/response schemas before integrating
  • Production systems requiring SLA guarantees or documented error handling

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no documentation for request body schema, response format, or what data is actually returned. All doc/pricing/API pages beyond the landing page are empty. The endpoint is narrowly scoped to a single Stripe customer ID with no explanation of what that means.

Warnings

  • No request or response schema documented — actual payload structure is unknown.
  • All documentation pages (/docs, /api, /pricing, /README) are effectively empty, showing only 'Connect wallet'.
  • Endpoint is scoped to a single hardcoded Stripe customer ID (75); unclear if this is a demo or production resource.
  • No OpenAPI spec, no ai-plugin manifest, no robots.txt, no agents.txt found.
  • The relationship between this Stripe customer endpoint and the broader advertised API categories (AI, analytics, etc.) is unclear.

Citations

Provenance

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

Agent access