x402basequality 0.30

x402-gated Stripe customer data endpoint on Base, paid per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/stripe/customers/96

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 96) 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 specific endpoint `/api/v1/stripe/customers/96` is listed as "Premium API Access" and costs up to 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The broader lowpaymentfee.com platform advertises a uniform $0.02/request pricing model across a wide catalog of endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities. The platform emphasizes no API keys, no rate limits, and instant access — all gated purely by x402 micropayments.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the Stripe customer endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but the actual behavior and data returned after payment remain unknown.

Capabilities

x402-paymentusdc-basestripe-customer-dataper-call-micropaymentjson-response

Use cases

  • —Retrieving Stripe customer details for customer ID 96 via a single micropayment
  • —Demonstrating x402 payment-gated API access patterns
  • —Programmatic access to payment platform customer records without API keys

Fit

Best for

  • —Developers experimenting with x402 protocol integrations
  • —Agents needing one-off Stripe customer data lookups without subscription overhead
  • —Projects exploring micropayment-gated API architectures

Not for

  • —Bulk Stripe customer data retrieval (single customer ID only)
  • —Users who need detailed API documentation or schema guarantees before integrating
  • —Production systems requiring SLA-backed uptime and support

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/customers/96
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 examples. The purpose of exposing a single Stripe customer record (ID 96) is unclear and potentially a demo or test resource.

Warnings

  • —No API documentation available — all doc pages return only 'Connect wallet'
  • —No OpenAPI or output schema provided; response format is completely unknown
  • —Endpoint targets a single hardcoded Stripe customer ID (96), which may be a test/demo resource
  • —No information on what data is actually returned after successful payment
  • —The broader platform lists many endpoints but none have documented schemas

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/G5UgE3
x402-gated Stripe customer data endpoint on Base, paid per-call in USDC. — Clawmart · Clawmart