Company earnings data via x402 micropayment on Base network, $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides company earnings data through the path `/api/v1/finance/C/earnings`. It is part of a broader suite of Finance & Web3 APIs offered by the provider, which also includes price feeds, exchange rates, token quotes, and gas estimates. The endpoint is gated by the x402 payment protocol: callers must include an X-PAYMENT header with a USDC payment on the Base network to receive a response.
The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which has 6 decimals), equating to $0.02 per request. This is consistent with the provider's site-wide pricing of $0.02/request. The endpoint accepts POST requests and returns application/json. No API keys or rate limits are advertised; access is purely pay-per-call.
The specific data returned by the `/finance/C/earnings` path is not documented in the crawled material. The "C" in the path likely refers to a ticker symbol or company identifier, and "earnings" suggests financial earnings data (e.g., quarterly or annual earnings reports). However, no response schema, example payloads, or detailed documentation were found — the docs, pricing, and API pages all rendered only a "Connect wallet" prompt with no further content. This limits confidence in the exact output format and data coverage.
Capabilities
Use cases
- —Retrieving company earnings data on-demand without API key registration
- —Integrating earnings information into trading bots or financial dashboards
- —Agent-driven financial research requiring per-call payment
Fit
Best for
- —Developers who want keyless, pay-per-call access to earnings data
- —AI agents that can settle x402 USDC payments on Base
- —Quick lookups of company earnings without subscription commitments
Not for
- —Bulk historical earnings data retrieval (no documented batch endpoint)
- —Users who cannot transact in USDC on the Base network
- —Applications requiring well-documented response schemas before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/finance/C/earnings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation of request parameters, response schema, or example payloads. The docs pages returned only 'Connect wallet' with no usable content. The exact nature of the earnings data is inferred from the URL path alone.
Warnings
- —No response schema or example response available — output format is unknown
- —Documentation pages (/docs, /api, /pricing, /README) all render only 'Connect wallet' with no actual content
- —The path segment 'C' in /finance/C/earnings is unexplained — it may be a placeholder ticker or a fixed identifier
- —Provider offers many endpoints but none have detailed public documentation
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/finance/C/earnings
- —Site-wide pricing is $0.02 per request with no API keys, no rate limits, and no minimumshttps://lowpaymentfee.com
- —The endpoint is categorized under Finance & Web3 alongside price feeds, exchange rates, token quotes, and gas estimateshttps://lowpaymentfee.com