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/71/transactions

What it does

This endpoint at lowpaymentfee.com exposes a card-transactions resource at `/api/v1/cards/71/transactions` behind an x402 payment challenge. It is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 protocol on the Base network.

The specific endpoint probed here accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (contract `0x8335…2913` on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform's landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required.

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, and no usage examples available. The endpoint's purpose ("card transactions") and expected input/output formats must be inferred from the URL path alone. The platform appears to be a demonstration or early-stage x402 marketplace rather than a mature, well-documented API provider.

Capabilities

x402-paymentusdc-basepay-per-requestcard-transactionspost-json

Use cases

  • —Querying card transaction data via a pay-per-request model without API keys
  • —Integrating x402-compatible agents that can autonomously pay for API access
  • —Testing x402 protocol payment flows on Base mainnet

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call API access on Base
  • —Prototyping micropayment-gated API workflows

Not for

  • —Production workloads requiring well-documented, stable APIs with SLAs
  • —Use cases needing detailed request/response schemas and error handling documentation
  • —High-volume consumers who need bulk pricing or rate-limit guarantees

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the docs pages are empty. The endpoint's actual functionality (what 'card transactions' means, what inputs it expects) is entirely opaque.

Warnings

  • —No OpenAPI or schema documentation available — request/response formats are unknown
  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • —The specific purpose of '/api/v1/cards/71/transactions' is unclear — 'Premium API Access' is a generic label
  • —Platform appears to be early-stage or a demo; reliability and data quality are unverifiable

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/n8cZHY