x402-gated card-transactions endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a card-transactions resource at `/api/v1/cards/95/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 priced at $0.02 per request and settled in USDC on the Base network.
The specific endpoint listed here (`/cards/95/transactions`) appears to be a financial or card-related transactions resource. The x402 challenge confirms it accepts POST requests, charges up to 20,000 base units of USDC (i.e., $0.02 given USDC's 6 decimals), and pays out to a specified Ethereum address on Base. No API keys or rate limits are advertised; access is gated purely by the x402 micropayment protocol.
Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the card-transactions endpoint actually returns or what POST body it expects. The platform's landing page lists many endpoints but provides no detail beyond names and prices. As a result, the actual functionality and data returned by this specific endpoint remain unclear.
Capabilities
Use cases
- —Retrieving card transaction data via a single micropayment-gated POST call
- —Integrating card transaction lookups into agent workflows without API key management
- —Programmatic access to card-level transaction records settled on Base L2
Fit
Best for
- —Developers wanting keyless, pay-per-use card transaction data
- —AI agents that can settle x402 micropayments on Base
- —Prototyping financial data integrations without subscription commitments
Not for
- —Production use cases requiring documented request/response schemas
- —High-volume batch processing where per-request pricing is inefficient
- —Users who need detailed API documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/cards/95/transactions \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI schema, no request/response documentation, no examples, and the docs pages are empty. The purpose of this specific card-transactions endpoint is not explained anywhere. This is effectively a stub listing.
Warnings
- —No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content
- —No OpenAPI or request/response schema provided; request body format for POST is unknown
- —The specific purpose and data returned by /api/v1/cards/95/transactions is undocumented
- —The endpoint path references a hardcoded card ID (95), which may indicate a demo or placeholder resource
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/cards/95/transactions
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/cards/95/transactions