Pay-per-call premium API access on Base via x402 — $0.02/request in USDC.
What it does
This endpoint at lowpaymentfee.com provides "Premium API Access" via the x402 payment protocol. The site hosts a broad catalog of pay-per-call APIs spanning data & analytics, AI/ML inference, finance & Web3 data, and infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required; callers simply attach an x402 payment header to each request.
The specific endpoint `/api/v1/wire/159` is listed as "Premium API Access" with a max amount of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals). The x402 challenge confirms the endpoint is live, accepts POST requests, and settles payments to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The payment timeout is 300 seconds.
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 schema, no request/response examples, and no description of what `/api/v1/wire/159` actually returns or what input it expects beyond a POST body. The endpoint's purpose beyond the generic label "Premium API Access" is unknown. Prospective callers should be aware that without documentation, the actual functionality and expected input format must be discovered experimentally.
Capabilities
Use cases
- —Programmatic access to a pay-per-call API without needing API keys or subscriptions
- —Agent-driven workflows that settle per-request costs in USDC on Base
- —Exploring x402 protocol integration with a low-cost endpoint
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents that need keyless, pay-as-you-go API access
- —Low-cost per-request API consumption on Base
Not for
- —Users who need detailed API documentation or guaranteed SLAs
- —Applications requiring well-defined request/response schemas before integration
- —High-throughput use cases where per-call crypto settlement adds unacceptable latency
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wire/159 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The x402 challenge is live and confirms pricing and payment details, but there is zero documentation on what this endpoint actually does, no OpenAPI schema, no request/response examples, and the docs pages are empty. The listing is effectively a stub with only payment metadata available.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content
- —No OpenAPI or input/output schema provided; the actual functionality of /api/v1/wire/159 is unknown
- —The generic label 'Premium API Access' does not describe what the endpoint returns
- —Cannot verify what data or service is delivered after payment
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/wire/159
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/wire/159
- —Docs, pricing, API, and README pages render only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs