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

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe customer resource (customer ID 187) behind an x402 paywall. The endpoint 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 x402 challenge for this specific endpoint shows a maxAmountRequired of 20000 base units of USDC (6 decimals), which equals $0.02 USD, consistent with the site's advertised pricing.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no explanation of what data the Stripe customers endpoint actually returns or what POST body it expects. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to determine the actual functionality or expected input format.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-customer-dataper-call-pricingjson-response

Use cases

  • Retrieving Stripe customer information via a pay-per-call model
  • Programmatic access to customer records without API key management
  • Agent-driven payment flows using x402 on Base

Fit

Best for

  • Developers wanting keyless, pay-per-request access to Stripe customer data
  • AI agents that can settle x402 payments in USDC on Base
  • Prototyping micropayment-gated API workflows

Not for

  • Production Stripe integrations where you already have direct Stripe API access
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • High-volume batch retrieval where per-call pricing is inefficient

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/customers/187 \
  -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 with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no explanation of what the endpoint actually returns. The purpose ('Stripe customers/187') is opaque without further context.

Warnings

  • No API documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet'
  • No OpenAPI or input/output schema provided; request body format is unknown
  • Endpoint path references a specific Stripe customer ID (187) — unclear if this is a demo or production resource
  • No robots.txt or agents.txt found
  • Purpose and returned data of this endpoint are not documented anywhere in the crawl

Citations

Provenance

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

Agent access