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 collection of pay-per-request APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities, all priced at $0.02 per request and 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/payments/268` is labeled "Premium API Access" in the x402 challenge. The challenge confirms it accepts USDC (contract 0x8335…2913 on Base) with a maxAmountRequired of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns application/json.
However, the exact functionality behind this particular `/payments/268` path is unclear. The site's landing page lists many distinct API paths (analytics, AI, finance, utilities) but does not specifically document a `/payments/268` route. There is no OpenAPI spec, no detailed request/response schema, and the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. Without documentation of what this endpoint actually returns or what input it expects, callers should treat this as a minimally documented paid endpoint.
Capabilities
Use cases
- —Accessing paid API services without API key registration
- —Making one-off paid requests settled in USDC on Base
- —Integrating pay-per-call endpoints into agent workflows
Fit
Best for
- —Developers who want keyless, pay-per-request API access
- —AI agents with x402-compatible payment capabilities
- —Users who prefer crypto micropayments over subscription billing
Not for
- —Users who need detailed API documentation before integrating
- —Anyone without USDC on the Base network
- —High-volume use cases where per-request pricing may add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/payments/268 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is no OpenAPI spec, no request/response schema, no documentation of what this specific endpoint does or returns, and the docs pages are empty. The endpoint path '/payments/268' is not listed among the site's advertised APIs, making its purpose unclear.
Warnings
- —No OpenAPI or schema documentation available
- —The /payments/268 path is not listed among the site's advertised API endpoints — its specific functionality is unknown
- —Docs, pricing, API, and README pages all render only 'Connect wallet' with no usable content
- —No request body schema or response schema provided — callers cannot know what to send or expect back
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/payments/268
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/payments/268
- —Site advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Site lists APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com