x402basequality 0.30

x402-gated Stripe invoice endpoint on Base, pay-per-call with USDC.

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

What it does

This endpoint at lowpaymentfee.com provides a pay-per-request API for Stripe invoice data, gated by the x402 protocol. The specific resource `/api/v1/stripe/invoices/40` is described as "Premium API Access" and accepts POST requests. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with an exact payment 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 x402-gated APIs spanning data & analytics, AI & machine learning (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request. The platform emphasizes no API keys, no rate limits, and instant access.

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 schema, no request/response examples, and no detailed description of what the `/api/v1/stripe/invoices/40` endpoint actually returns. The endpoint is live (returns a valid 402 x402 challenge), but the lack of documentation makes it difficult to know what data to send or expect back.

Capabilities

x402-paymentusdc-base-networkstripe-invoicespay-per-requestno-api-key

Use cases

  • —Retrieving Stripe invoice data via a single paid API call
  • —Agent-driven invoice lookups without API key management
  • —Programmatic access to invoice information settled with USDC on Base

Fit

Best for

  • —Agents or services that need on-demand Stripe invoice data without subscription commitments
  • —Developers experimenting with x402 payment-gated APIs
  • —Use cases requiring keyless, pay-per-request access

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need bulk or batch invoice processing at scale
  • —Anyone needing non-crypto payment options

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no OpenAPI schema, no request/response examples, and all documentation pages are empty beyond a wallet-connect prompt. The purpose of this specific endpoint (Stripe invoices/40) is unclear, and there is no way to determine the expected request body or response format from available materials.

Warnings

  • —No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
  • —No OpenAPI or schema describing request body or response format
  • —Purpose of '/api/v1/stripe/invoices/40' is ambiguous — unclear what invoice data is returned or what '40' refers to
  • —The broader platform lists many endpoints but none have documented schemas or examples

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/Sr9qNC
x402-gated Stripe invoice endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart