After configuring your scenario matrix in the Oracle tool, you can request an AI reading that interprets the full grid of projections and distills it into a decisive five-part strategic assessment. The Oracle speaks like a trader reviewing a position — direct, specific, and opinionated. It does not teach you the game; it tells you what to do given the numbers you have set.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/natureloved/HashPilot/llms.txt
Use this file to discover all available pages before exploring further.
How a reading is triggered
The Oracle reading is initiated from the Oracle tool page after you have set your four slider values and the nine cells of the scenario matrix are populated. Clicking the reading button sends your complete input state to the/api/oracle endpoint, which passes it to the AI and returns a plain-text reading in a structured format.
Set your sliders
Dial in the four scenario variables: Network Growth %, Price Move %, New Players entering the game, and number of Halvings to model. These define the macro conditions the Oracle reasons about.
Review the matrix
The Oracle matrix is a 3×3 grid of Bear / Base / Bull scenarios across 30-day, 90-day, and 180-day time horizons. Each cell shows projected hCASH earnings, USD value, and your estimated network share. Confirm the numbers look right before requesting a reading.
Request the reading
Submit the matrix to the Oracle. The AI processes your full slider state and the three diagonal scenario anchors (Bear 30d, Base 90d, Bull 180d) and returns a reading within a few seconds.
Reading format
Every Oracle reading follows the same five-section structure. There is no prose padding — each section is a single focused output.VERDICT
A one-sentence directional call: BULLISH, BEARISH, or UNCERTAIN, with the core reason. This is the Oracle’s overall read on whether your current setup is positioned well under the modeled conditions.
CRITICAL FACTOR
The single slider variable with the highest impact on your outcome spread across the matrix. This tells you which assumption to challenge first if you want to stress-test the reading.
BEST MOVE
One specific action to take now given the matrix projections. Not a general suggestion — a named action such as claiming before a halving, upgrading a facility tier, or buying hashrate on the secondary market.
RISK ALERT
The scenario you are most exposed to and least prepared for. Usually references the Bear column — tells you what to hedge against even if the base case looks good.
ORACLE CONFIDENCE
HIGH, MEDIUM, or LOW — with a one-sentence explanation of why. Low confidence typically means the slider inputs produce a wide outcome spread with no clear dominant scenario.
Formatting rules
The Oracle uses ALL CAPS for emphasis and plain text throughout. No markdown symbols, no bullet points, no headers. The raw text is rendered directly in the terminal interface.
Sample reading
This is an example of a full Oracle reading returned by the API given moderately bullish slider inputs with a halving on the horizon.Interpreting each section
VERDICT — what it means and when to trust it
VERDICT — what it means and when to trust it
BULLISH means the matrix shows your setup outperforming relative to your current position under most modeled scenarios. BEARISH means the numbers skew against you. UNCERTAIN means the scenarios diverge enough that no clear call is warranted.Trust the verdict more when ORACLE CONFIDENCE is HIGH. When confidence is LOW or MEDIUM, treat the VERDICT as a lean rather than a conclusion, and weight the RISK ALERT more heavily.
CRITICAL FACTOR — how to use it
CRITICAL FACTOR — how to use it
This is the Oracle telling you which slider to scrutinize. If the critical factor is HALVINGS, go to the Halving Tracker and confirm how many blocks remain. If it is NETWORK GROWTH, check recent player activity and hashrate trend data on the dashboard.Adjust the identified slider by ±20% and request a new reading to see how sensitive your outlook is to that single assumption.
BEST MOVE — specificity and limitations
BEST MOVE — specificity and limitations
The BEST MOVE is derived from the diagonal of your matrix — the Bear 30d, Base 90d, and Bull 180d cells — and the slider state. It is the most actionable section of the reading.It does not account for your live unclaimed balance or current electricity rate, because the Oracle receives only the slider and matrix data. Cross-reference it against your current rate in the Claim Advisor before acting on a CLAIM or HOLD recommendation.
RISK ALERT — preparing for the downside
RISK ALERT — preparing for the downside
The Oracle always identifies the scenario worth hedging even when the verdict is bullish. Read the RISK ALERT as: “If this specific thing happens, here is how it will hurt you.”A common RISK ALERT pattern is network dilution from new player inflow collapsing your hashrate share faster than projected. The antidote is always more hashrate or faster claiming — the Oracle will name whichever applies.
ORACLE CONFIDENCE — why it varies
ORACLE CONFIDENCE — why it varies
HIGH confidence means the matrix scenarios converge — your outcome is relatively predictable across the range. MEDIUM means the scenarios spread but the direction is still clear. LOW means the inputs produce wildly different outcomes depending on which scenario materializes.Low confidence is not a failure state. It is the Oracle telling you that your setup is highly sensitive to market conditions and that now is not the time for large, irreversible decisions.
API reference
POST /api/oracle
Submits a scenario matrix and slider configuration to the Oracle AI and returns a structured plain-text reading.This endpoint requires
ANTHROPIC_API_KEY in your environment. See API Keys setup. Unlike the chat endpoint, the Oracle response is not streamed — it returns when the full reading is complete.The four macro scenario variables set by the user in the Oracle tool.
Projected growth in total network hashrate, expressed as a percentage. For example,
25 means 25% network hashrate growth modeled over the scenario window.Projected hCASH price change, expressed as a percentage. Positive values are bullish, negative values are bearish. For example,
-30 models a 30% price decline.Estimated number of new players joining the network within the scenario window. Higher values increase network dilution risk.
Number of halvings expected to occur within the scenario window.
0 means no halving; 1 means one halving fires during the modeled period.A 3×3 nested array of scenario cells. The outer array index corresponds to the scenario row (0 = Bear, 1 = Base, 2 = Bull). The inner array index corresponds to the time horizon column (0 = 30d, 1 = 90d, 2 = 180d).The Oracle reads from three diagonal cells:
matrix[0][0] (Bear 30d), matrix[1][1] (Base 90d), and matrix[2][2] (Bull 180d).Each cell object has the following fields:Projected hCASH earned in this scenario and time window.
USD value of projected hCASH earnings at the modeled price.
Estimated network hashrate share as a percentage.
Scenario label. One of
"bear", "base", or "bull".Time horizon in days. One of
30, 90, or 180.The complete Oracle reading as a plain-text string. The text follows the five-section format: VERDICT, CRITICAL FACTOR, BEST MOVE, RISK ALERT, and ORACLE CONFIDENCE. Sections are separated by line breaks. No markdown characters are present.
500. Usually caused by a missing ANTHROPIC_API_KEY or a downstream Anthropic API failure.