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/198

What it does

This endpoint at lowpaymentfee.com provides access to a specific Stripe invoice resource (invoice ID 198) 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 specific endpoint `/api/v1/stripe/invoices/198` is listed as "Premium API Access" and costs up to 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). This is consistent with the site-wide pricing of $0.02 per request advertised on the provider's landing page. The provider offers a broader catalog of APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all at the same $0.02/request price point and all gated via x402 on Base.

Documentation is extremely sparse. The /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the Stripe invoice endpoint actually returns. The endpoint is confirmed live (returns a valid 402 challenge), but without documentation it is unclear what data the invoice endpoint provides or what POST body it expects.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-invoice-datajson-responseper-call-pricing

Use cases

  • —Retrieving Stripe invoice data (invoice 198) via a single micropayment
  • —Agent-driven invoice lookups without API key management
  • —Programmatic access to invoice details settled in USDC on Base

Fit

Best for

  • —Agents or bots that need keyless, pay-per-call access to invoice data
  • —Developers experimenting with x402 payment flows on Base
  • —Scenarios where avoiding API key provisioning is valuable

Not for

  • —Bulk invoice retrieval or batch processing (single invoice endpoint only)
  • —Users who need detailed API documentation or guaranteed SLAs
  • —Production workflows requiring well-documented request/response schemas

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — every doc page shows only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The specific purpose of the Stripe invoice endpoint is unclear beyond its title.

Warnings

  • —No API documentation available; all doc pages render only 'Connect wallet'
  • —No OpenAPI or schema definition found
  • —Unknown request body format — no input schema documented
  • —Unknown response format — no output examples or schema available
  • —Single-resource endpoint (invoice 198) with no explanation of what data it returns
  • —Provider site appears to be a demo or early-stage project with minimal content

Citations

Provenance

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

Agent access

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