x402basequality 0.30

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

What it does

This endpoint at lowpaymentfee.com exposes a card-transactions resource at `/api/v1/cards/12/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…), which equals $0.02 per request (USDC uses 6 decimals). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The provider's landing page lists a broad catalog of x402-gated APIs spanning data/analytics, AI/ML, finance/Web3, and infrastructure utilities—all priced at $0.02 per call. This specific endpoint appears under a "cards" resource path, suggesting it returns transaction records associated with a card entity (card ID 12). However, no OpenAPI schema, request/response examples, or detailed documentation were found in the crawl. The docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no further content.

Because the endpoint is live (returning a well-formed 402 challenge) but lacks any documentation about the request body format or response structure, consumers will need to experiment or contact the provider to understand the expected input and output. The pricing model is straightforward: no API keys, no rate limits, pay-per-request via x402 on Base.

Capabilities

x402-paymentusdc-basecard-transactionspay-per-requestno-api-key

Use cases

  • —Retrieving transaction records for a specific card entity
  • —Programmatic access to card transaction data without API key management
  • —Agent-driven financial data retrieval with per-call USDC payment

Fit

Best for

  • —Agents that need card transaction data and can pay per-call via x402
  • —Developers wanting keyless, pay-as-you-go API access on Base
  • —Prototyping financial integrations without subscription commitments

Not for

  • —Production use cases requiring documented request/response schemas
  • —High-volume batch processing where per-call pricing is inefficient
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the card-transactions resource actually returns. The docs pages are empty. This is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available for this endpoint
  • —No request body format or response structure documented anywhere in the crawl
  • —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
  • —The specific resource '/api/v1/cards/12/transactions' is not listed on the provider's landing page catalog, raising questions about its purpose
  • —Cannot verify what data this endpoint actually returns without making a paid request

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:53:38Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

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