Send use case
Briefly describe newsletter, dashboard, app, community, or research workflow.
The WHYCRYPTO API provides structured market explanations for newsletters, communities, dashboards, and research products: cause, amplifier, confirmation, confidence, source quality, and historical WHY context. No signal product, no predictions, no financial advice.
The primary endpoint returns the current Bitcoin explanation as a structured Cause → Amplifier → Confirmation payload. Authentication uses an API key.
curl -s https://why-crypto.com/api/v1/why/bitcoin \ -H "X-API-Key: why_live_YOUR_API_KEY"
Briefly describe newsletter, dashboard, app, community, or research workflow.
Define starter limits and required endpoints before production use starts.
Validate WHY, history, compare, and briefing payloads with real guardrails.
Measure usage, errors, rate limits, and lead status in admin.
/api/v1/explainabilityFramework, auth, rate limits./api/v1/why/{asset}Current asset explanation./api/v1/history/{asset}Historical WHY entries./api/v1/compareComparative explainability./api/v1/briefingDaily WHY briefing payload.Fields like cause, amplifier, confirmation, and confidence stay stable.
Plaintext keys are not stored and are shown only once.
Requests, errors, limits, and top endpoints are measured in admin.
Starter, Pro, Business, and Enterprise get separate quotas.
Versioned WHY payloads with scores, source quality, and guardrails.
BTC WHY, Daily WHY, and Top Movers as branded copy/paste widgets.
Short Cause → Amplifier → Confirmation blocks for editorial workflows.
Teams can request API access, quotas, and widget usage to embed WHYCRYPTO explanations into products, newsletters, or dashboards in a controlled way.