x402basequality 0.30

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

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

What it does

This endpoint at lowpaymentfee.com provides access to a Stripe invoice resource (invoice ID 190) 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 maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services—all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the Stripe invoices endpoint at path `/api/v1/stripe/invoices/190`, which is not listed among the publicly advertised API categories on the homepage. Its exact response payload and purpose are unclear from available documentation.

Documentation is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response examples, and no detailed description of what the Stripe invoices endpoint returns. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual functionality behind the paywall cannot be verified from the crawl material alone.

Capabilities

x402-paymentusdc-on-basestripe-invoice-accesspay-per-requestjson-response

Use cases

  • —Retrieving Stripe invoice data programmatically via a pay-per-call model
  • —Agents that need to fetch invoice details without managing API keys
  • —Demonstrating x402 payment protocol integration with USDC on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-request access to invoice data
  • —Projects already operating on the Base L2 network with USDC

Not for

  • —Users needing well-documented, production-grade Stripe integrations
  • —Bulk invoice retrieval where per-call pricing is inefficient
  • —Anyone requiring detailed API documentation before committing

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/stripe/invoices/190
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no request/response examples, and no documentation beyond a wallet-connect prompt. The specific Stripe invoices endpoint is not listed on the homepage's advertised APIs, making its purpose unclear. Effectively a stub listing.

Warnings

  • —No OpenAPI spec or schema available for this endpoint
  • —Documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —This specific endpoint (/api/v1/stripe/invoices/190) is not listed among the provider's publicly advertised APIs
  • —Actual response payload and functionality behind the paywall are unknown
  • —The endpoint path references a specific invoice ID (190), which may indicate a demo or test resource

Citations

Provenance

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

Agent access

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