What the API provides
Six authenticated calculation routes apply explicit formulas to the numbers supplied in a JSON request. Each result includes values, the formula and model assumptions. Calculation calls do not connect to an exchange or need permission to redistribute a provider feed.
Optional market routes normalize selected order books and completed candles, and derive visible-depth liquidity measures. These routes require the research plan and a provider that the operator has explicitly enabled after reviewing redistribution rights. The default configuration enables no paid market-data providers.
Access follows a written agreement
Contact the operator through the About page to discuss availability, a quote, the intended use, expiry, monthly request allowance and per-minute allowance. There is no automatic checkout or payment collection on this page. An API key is issued manually only after the operator verifies the agreed invoice payment.
Keep the key in your own server environment. Do not place it in public JavaScript, share links, query strings or a mobile application that cannot protect a shared credential. These keys grant research API access; they do not grant access to any exchange account.
Start with the public endpoints
GET /api/v1/health checks this deployment and its access database. GET /api/v1/capabilities describes routes and currently enabled provider adapters. A successful health response does not establish that every upstream provider is reachable.
Read the authentication and error contract before integration. A static website deployment alone does not start the optional Python service, so the status page may correctly report that the API is unavailable until the operator deploys it.