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

What it does

This endpoint at lowpaymentfee.com provides access to a Stripe invoice resource (invoice ID 160) behind an x402 paywall. The endpoint accepts POST requests and returns application/json responses. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme.

The specific endpoint `/api/v1/stripe/invoices/160` is labeled "Premium API Access" and costs up to 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The broader lowpaymentfee.com platform advertises a suite of APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The exact behavior of this Stripe invoices endpoint — what input it expects and what invoice data it returns — is not documented. The x402 challenge is live and well-formed, confirming the endpoint is operational.

Capabilities

x402-paymentusdc-base-networkstripe-invoicesper-request-billingno-api-keyjson-response

Use cases

  • —Retrieving Stripe invoice data via a pay-per-call model without API key management
  • —Programmatic access to invoice #160 details settled in USDC on Base
  • —Agent-driven invoice retrieval where payment is handled inline via x402 protocol

Fit

Best for

  • —Developers wanting keyless, pay-per-use access to Stripe invoice data
  • —AI agents that can settle x402 payments in USDC on Base
  • —Prototyping micropayment-gated API workflows

Not for

  • —Users needing detailed API documentation or OpenAPI specs before integrating
  • —Bulk invoice retrieval across many invoice IDs (only invoice 160 is exposed at this path)
  • —Users without USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/stripe/invoices/160
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment to access.

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint works. However, there is zero documentation on request/response schemas, no OpenAPI spec, and the docs/pricing/README pages are all blank beyond a wallet connect prompt. The purpose and output of this specific Stripe invoices endpoint is unclear.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet'
  • —No OpenAPI or JSON schema for request or response payloads
  • —The specific behavior of /api/v1/stripe/invoices/160 is undocumented — unclear what data is returned
  • —The endpoint is scoped to a single invoice ID (160); generalizability is unknown

Citations

Provenance

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

Agent access

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