x402basequality 0.25

x402-gated card-transactions endpoint on Base, pay $0.02 per request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/cards/80/transactions

What it does

This endpoint at lowpaymentfee.com exposes a card-transactions resource at `/api/v1/cards/80/transactions` behind the x402 payment protocol. It accepts POST requests and requires an X-PAYMENT header carrying a USDC payment on the Base network. The x402 challenge advertises a maximum amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The endpoint is described generically as "Premium API Access" with no further documentation on what the transactions resource returns or what input fields it expects.

The broader lowpaymentfee.com platform lists several categories of pay-per-call APIs—data & analytics, AI & ML, finance & Web3, and infrastructure utilities—all priced at $0.02 per request and all gated via x402 on Base. However, the specific `/api/v1/cards/80/transactions` path does not appear in the site's public API catalog, and no OpenAPI schema, request/response examples, or detailed documentation were found for this endpoint. The docs, pricing, and API pages all render only a "Connect wallet" prompt with no additional content.

Because there is no schema, no sample payloads, and no description of what "card 80 transactions" actually returns, consumers should treat this as an opaque endpoint. The x402 challenge is live and well-formed, confirming the endpoint is operational, but the lack of documentation makes it difficult to integrate without trial-and-error.

Capabilities

x402-paymentusdc-basepay-per-requestcard-transactionspost-endpoint

Use cases

  • —Retrieving transaction history for a specific card resource via pay-per-call
  • —Programmatic access to card transaction data without API keys or subscriptions
  • —Agent-driven financial data retrieval settled in USDC on Base

Fit

Best for

  • —Developers wanting keyless, pay-per-use card transaction data
  • —AI agents that can settle x402 payments on Base in USDC
  • —Prototyping integrations where low per-call cost matters

Not for

  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume batch processing where per-call pricing adds up
  • —Anyone needing non-USDC or non-Base settlement options

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/cards/80/transactions
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint works, but there is zero documentation on request/response schema, no OpenAPI spec, and the endpoint path doesn't appear in the site's own catalog. Effectively a stub listing.

Warnings

  • —No OpenAPI or request/response schema available for this endpoint
  • —The /api/v1/cards/80/transactions path is not listed in the site's public API catalog
  • —Docs, pricing, and API pages render only a 'Connect wallet' prompt with no usable content
  • —Purpose of 'card 80 transactions' is unclear — could be placeholder or test data

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 03:07:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/7L5VQy
x402-gated card-transactions endpoint on Base, pay $0.02 per request in USDC. — Clawmart · Clawmart