CVS Health earnings data via x402 micropayment on Base network, $0.02 per request.
What it does
This endpoint provides CVS Health (ticker: CVS) earnings data through the x402 payment protocol. It is hosted on lowpaymentfee.com, a platform offering a variety of pay-per-call API endpoints spanning finance, analytics, AI/ML, and utility services. Each request is settled on the Base network using USDC at a cost of $0.02 per call, with no API keys, rate limits, or subscriptions required.
The specific endpoint `/api/v1/finance/CVS/earnings` returns earnings-related financial data for CVS Health. The x402 challenge confirms the endpoint is live and accepts POST requests. Payment is made via an `X-PAYMENT` header using the x402 "exact" scheme, settling to a specified address in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on the Base L2 network. The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02.
Documentation on the site is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI schema, no example request/response payloads, and no description of the earnings data fields returned. The endpoint's actual response format and data coverage (e.g., historical quarters, EPS, revenue) are unknown and must be discovered by making a paid call.
Capabilities
Use cases
- —Retrieving CVS Health earnings data for financial analysis
- —Automated portfolio monitoring that needs per-stock earnings on demand
- —Agent-driven research workflows requiring pay-per-call financial data
Fit
Best for
- —AI agents needing on-demand CVS earnings without API key management
- —Developers who want pay-per-use financial data with no subscription
- —Crypto-native applications settling micropayments on Base
Not for
- —Bulk historical earnings data across many tickers (only CVS endpoint documented here)
- —Users without a Base-network USDC wallet
- —Applications requiring detailed API documentation or SLAs before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/finance/CVS/earnings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no example request/response, and the docs pages are empty stubs. The actual data returned is completely unknown, making this effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or output schema provided; response format is unknown
- —No example request or response payloads available
- —Endpoint specificity (CVS only) is unclear — the URL pattern suggests per-ticker endpoints but this is unconfirmed
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/finance/CVS/earnings
- —The maximum amount required is 20,000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/finance/CVS/earnings
- —The platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/finance/CVS/earnings
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs