x402basequality 0.25

x402-gated Stripe invoice 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 "Premium API Access" behind an x402 paywall. The specific resource `/api/v1/stripe/invoices/75` appears to be a Stripe invoice-related API call, though the exact functionality is not documented beyond the generic label. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.

The hosting site lowpaymentfee.com offers a broad catalog of x402-gated APIs spanning data/analytics, AI/ML (sentiment, summarization, classification, embeddings), finance/Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). Most listed endpoints cost $0.02 per request. This particular endpoint's x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site's uniform pricing.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema, and no usage examples. The endpoint is live (returns a proper 402 challenge), but without documentation it is unclear what request body is expected or what the response contains. The endpoint accepts POST requests.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-invoicesper-call-pricingno-api-key

Use cases

  • Programmatically accessing Stripe invoice data via a pay-per-call model
  • Agent-driven invoice retrieval without API key management
  • Micropayment-gated access to financial data

Fit

Best for

  • Agents that need one-off invoice lookups without subscription commitments
  • Developers exploring x402 payment protocol integrations
  • Use cases where no-API-key, pay-per-request access is preferred

Not for

  • Production workloads requiring documented request/response schemas
  • High-volume invoice processing where subscription pricing would be cheaper
  • Users who need detailed API documentation before integration

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request format, response schema, or what 'Premium API Access' for Stripe invoices actually returns. No OpenAPI spec, no examples, and all doc pages are empty wallet-connect stubs.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or request/response schema provided
  • Exact functionality of /api/v1/stripe/invoices/75 is undocumented
  • The endpoint path references a specific invoice ID (75); unclear if this is parameterized or fixed

Citations

Provenance

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

Agent access

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