x402basequality 0.30

x402-gated Stripe invoice endpoint on Base, paying $0.02 in USDC per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a Stripe invoice resource (invoice #183) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/stripe/invoices/183` is labeled "Premium API Access" and accepts HTTP POST requests. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the payment parameters (asset, amount, payTo address) and must attach a valid X-PAYMENT header to complete the transaction. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys or rate limits are advertised; access is gated purely by micropayment.

The platform advertises additional endpoints for sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, and more — all at the same $0.02 price point. However, documentation beyond the landing page is extremely sparse: the /docs, /api, /pricing, 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 invoice endpoint actually returns. The exact purpose of retrieving "Stripe invoice 183" is unclear from available materials.

Capabilities

x402-paymentusdc-basestripe-invoicepay-per-callno-api-key

Use cases

  • Programmatically retrieving a Stripe invoice record via micropayment
  • Agent-driven invoice lookup without traditional API key authentication
  • Demonstrating x402 protocol payment flows for invoice data

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that need one-off invoice data without subscription commitments
  • Testing micropayment-gated API integrations on Base

Not for

  • Bulk invoice processing requiring thousands of calls (no documented batch endpoint)
  • Users needing detailed API documentation or response schema guarantees
  • Production systems requiring SLA or uptime commitments

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/183 \
  -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 402 challenge, confirming it is operational. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page, and the purpose of this specific invoice endpoint is unclear. The docs, pricing, and README pages are all empty stubs.

Warnings

  • No OpenAPI or schema documentation available — response format is unknown
  • The /docs, /pricing, /api, and /README pages contain no useful content (only 'Connect wallet')
  • The specific purpose of '/api/v1/stripe/invoices/183' is unclear — it may be a demo or placeholder
  • No examples of request body or response body are available anywhere in crawled material

Citations

Provenance

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

Agent access