x402-gated card-transactions endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com exposes a POST resource at `/api/v1/cards/88/transactions` behind an x402 payment challenge. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (contract 0x8335…2913) on the Base network, which translates to $0.02 per request (USDC uses 6 decimals). Payment is made via the "exact" scheme, settling to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The provider's landing page lists a broad catalog of APIs spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all uniformly priced at $0.02 per request with no API keys, no rate limits, and instant access. However, the specific `/api/v1/cards/88/transactions` path is not listed among the advertised endpoints on the homepage, and its exact functionality is unclear. The title "Premium API Access" and the path segment "cards/88/transactions" suggest it may relate to card or financial transaction data, but no documentation, request schema, or response schema is available to confirm this.
Documentation pages (/docs, /api, /pricing, /README) all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response examples, and no detailed description of what this endpoint actually returns. Prospective callers should be aware that the endpoint is live (confirmed by the 402 challenge) but its behavior after payment is entirely undocumented.
Capabilities
Use cases
- —Fetching card or financial transaction data via a single paid POST request
- —Agent-driven workflows that need pay-per-call access without API key registration
- —Programmatic access to transaction records gated by USDC micropayments
Fit
Best for
- —Developers wanting keyless, pay-per-use API access on Base
- —AI agents with x402-compatible wallets needing financial data
- —Prototyping micropayment-gated API consumption
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —High-volume batch processing where per-request pricing may add up
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/cards/88/transactions \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on what the endpoint actually does, no request/response schema, and the specific path is not even listed on the provider's own homepage. Docs pages are empty. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README all return only a wallet-connect prompt with no content.
- —The specific path /api/v1/cards/88/transactions is not listed among the provider's advertised endpoints; its purpose is unknown.
- —No request or response schema is provided; callers cannot know what to send or what to expect back.
- —The broad catalog of endpoints on the homepage (AI, analytics, finance, utils) may be placeholder/demo content — none have been independently verified.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base with exact schemehttps://lowpaymentfee.com/api/v1/cards/88/transactions
- —Provider homepage lists uniform $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs