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

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" behind an x402 payment challenge. The specific resource path (`/api/v1/stripe/invoices/158`) suggests it returns or processes a Stripe invoice record (invoice #158). Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which at 6 decimals equals $0.02 USD per request.

The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing covers only the `/api/v1/stripe/invoices/158` endpoint, whose exact response payload is undocumented. The endpoint accepts POST requests and returns `application/json`.

Documentation on the site 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 spec, no request/response schema beyond the x402 challenge's `outputSchema` stub, and no examples of what the invoice endpoint actually returns. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data or functionality it provides beyond the generic "Premium API Access" label.

Capabilities

x402-paymentusdc-settlementbase-networkstripe-invoicepay-per-requestno-api-keyjson-response

Use cases

  • —Retrieving or processing a specific Stripe invoice via a crypto-settled pay-per-call model
  • —Demonstrating x402 payment protocol integration with USDC on Base
  • —Agent-driven invoice access without traditional API key authentication

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that can settle USDC payments on Base L2
  • —Use cases requiring keyless, pay-per-request invoice access

Not for

  • —Production invoice management requiring documented schemas and SLAs
  • —Users who need traditional API key or OAuth authentication
  • —Bulk invoice retrieval or batch processing (single invoice endpoint)

Quick start

# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# Without payment, it returns a 402 challenge.
curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/158 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <your-x402-payment-token>"

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation, no request/response schema, no examples, and the purpose of the specific invoice endpoint is unclear. The docs pages are empty beyond a wallet connect prompt.

Warnings

  • —No OpenAPI spec or request/response schema available
  • —Documentation pages (docs, API, pricing, README) all render only 'Connect wallet' with no content
  • —The specific functionality of /api/v1/stripe/invoices/158 is undocumented — unclear what data it returns
  • —Single hardcoded invoice ID (158) in the path suggests this may be a demo or test endpoint

Citations

Provenance

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

Agent access

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