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 44) via a POST request. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all gated behind x402 payment challenges on the Base network.

The specific endpoint `/api/v1/stripe/customers/44` is labeled "Premium API Access" and returns an x402 challenge requiring payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. Payment is settled on-chain to the specified wallet address. The platform advertises no API keys, no rate limits, and instant access — the only gate is the per-request USDC micropayment.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no description of what data this particular endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but without documentation it is unclear what request body is expected or what the response payload looks like.

Capabilities

x402-paymentusdc-micropaymentbase-networkstripe-customer-dataper-request-billingno-api-key

Use cases

  • Retrieving Stripe customer information via a crypto-micropayment gate
  • Programmatic access to payment/customer data without traditional API keys
  • Agent-driven workflows that need on-demand Stripe customer lookups settled in USDC

Fit

Best for

  • Developers who want keyless, pay-per-call access to Stripe customer data
  • AI agents with Base-network USDC wallets needing on-demand API calls
  • Projects exploring x402-protocol micropayment patterns

Not for

  • Users needing detailed API documentation or request/response schemas before integrating
  • High-volume batch Stripe data retrieval where per-call fees add up
  • Anyone without a Base-network USDC wallet

Quick start

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

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 spec, no request/response schema, and no explanation of what data this endpoint actually returns. The purpose of a '/stripe/customers/44' endpoint is unclear without further context.

Warnings

  • Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no usable content.
  • No OpenAPI or request/response schema available — request body format and response structure are unknown.
  • The endpoint path references a hardcoded Stripe customer ID (44), which may indicate a demo or placeholder rather than a general-purpose API.
  • The actual data returned by this endpoint is undocumented and unverifiable.

Citations

Provenance

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

Agent access