x402basequality 0.30

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 exposes a specific Stripe invoice resource (`/api/v1/stripe/invoices/144`) behind an x402 paywall. When called without payment, it returns a 402 challenge requesting USDC on the Base network. The endpoint accepts HTTP POST and returns `application/json`.

The price per request is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the "exact" scheme with a 300-second timeout. The provider's landing page advertises a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, and utility services — all at the same $0.02/request price point with no API keys, no rate limits, and no commitments.

However, this particular endpoint (`/stripe/invoices/144`) is not listed among the advertised APIs on the homepage. Its actual response payload is unknown — the title "Premium API Access" and the Stripe-invoice-style path suggest it may return invoice data or serve as a payment/billing resource, but no documentation, schema, or example responses are available. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content.

Capabilities

x402-paymentusdc-basestripe-invoiceper-call-pricingjson-responsehttp-post

Use cases

  • Retrieving Stripe invoice data (invoice #144) via a single micropayment
  • Programmatic access to invoice details without traditional API key management
  • Agent-driven payment and data retrieval in a single HTTP round-trip

Fit

Best for

  • Agents or services that need to fetch specific invoice data on-demand
  • Developers exploring x402 payment-gated API patterns on Base
  • Use cases where keyless, pay-per-call access is preferred over subscriptions

Not for

  • Bulk invoice retrieval or batch processing (single-resource endpoint)
  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • Non-crypto workflows that cannot settle USDC on Base

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a well-formed x402 challenge, but there is zero documentation on what the endpoint actually returns, no OpenAPI schema, no example responses, and the docs/pricing/README pages are empty. The specific invoice endpoint is not even listed among the provider's advertised APIs, making its purpose unclear.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • This specific endpoint (/api/v1/stripe/invoices/144) is not listed among the provider's advertised API catalog on the homepage.
  • Response schema and payload structure are completely unknown.
  • No OpenAPI spec or machine-readable schema is published.
  • The purpose and contents of 'invoice 144' are opaque — could be test data or a placeholder.

Citations

Provenance

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

Agent access