DAI OHLCV (open-high-low-close-volume) crypto market data via x402 micropayment on Base.
What it does
This endpoint provides OHLCV (Open, High, Low, Close, Volume) candlestick data for the DAI cryptocurrency token. It is part of the lowpaymentfee.com platform, which offers a suite of data, analytics, AI, finance, and utility APIs all gated behind the x402 payment protocol on the Base network.
The endpoint is live and returns a 402 challenge requesting payment in USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base). The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). Payment is made via the x402 "exact" scheme, with a 300-second timeout. No API keys or rate limits are advertised — access is purely pay-per-request.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no further content. The specific request body schema and response format for the DAI OHLCV endpoint are not documented anywhere in the crawled material. The endpoint accepts POST requests and returns application/json. Without documentation, the exact request parameters (e.g., time range, interval/granularity) and response fields must be inferred from the endpoint name and common OHLCV conventions.
Capabilities
Use cases
- —Fetching historical DAI price candles for charting or technical analysis
- —Feeding DAI OHLCV data into trading bots or algorithmic strategies
- —Building dashboards that display DAI price movements over time
Fit
Best for
- —Agents or apps needing on-demand DAI candlestick data without API key management
- —Micropayment-native workflows on Base that need crypto market data
- —Low-volume or sporadic queries where per-request pricing is more economical than subscriptions
Not for
- —High-frequency trading requiring sub-second latency and bulk historical downloads
- —Users who need OHLCV data for many tokens in a single call (this endpoint is DAI-specific)
- —Teams that require detailed API documentation and SLAs before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/crypto/DAI/ohlcv \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{}'Example
Request
{
"limit": 10,
"symbol": "DAI",
"interval": "1d"
}Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing ($0.02 USDC on Base). However, there is no documentation for request parameters or response schema — the docs pages are all blank wallet-connect stubs. The request example above is entirely inferred from OHLCV conventions and may not match the actual API contract.
Warnings
- —No API documentation available — all doc pages return only a 'Connect wallet' prompt with no content.
- —Request body schema and response format are unknown; the example_request_json is speculative based on common OHLCV conventions.
- —The endpoint is part of a platform with many diverse APIs (AI, analytics, finance, utils) all at $0.02 — the actual data sources and quality are unverified.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/crypto/DAI/ohlcv
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/crypto/DAI/ohlcv
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages all show only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs