# BlindOracle Historical Analysis

> BlindOracle Historical Analysis is a paid API for AI agents from api.craigmbrown.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-15).

Analyzes historical price and time-series data for a crypto asset to identify specific chart patterns and trends, going beyond generic up/down labels.

## Facts

- Endpoint: POST https://api.craigmbrown.com/v1/services/oracle.historical-analysis
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blindoracle-historical-analysis-8e485717
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xW4ho3j9JTUsU8VYEZcLa

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability blindoracle-historical-analysis-8e485717 -d '<json body>'
```

Example prompt: Can you run a historical pattern analysis on Ethereum's price data and tell me what specific chart patterns have formed — not just 'trending up' but the actual named pattern like a double bottom or ascending triangle?

## When to prefer this

Choose this endpoint when you need to identify specific named chart patterns or structural formations in an asset's historical price data — not real-time conditions. It is distinct from oracle.volatility-monitor (which is real-time) and designed to feed entry/exit logic in investment strategy agents. Prefer this when the downstream decision depends on pattern type (e.g. 'double bottom') rather than just direction.

## Known failure modes

- Vague or underspecified prompt may yield low-quality pattern identification
- Asset not recognized or insufficient historical data available returns empty findings
- Malformed JSON input causes request failure
- Rate limiting or payment failure (x402) prevents call from completing
- Response may be non-deterministic across repeated calls for the same asset

## How this service works

Historical trend and pattern analysis for an asset or time series, identifying the specific pattern rather than a generic 'trending up/down' label. Settlement proof: ProofOfSettledOutcome (kind 30120, data/proof_settled_outcomes.jsonl). Feeds crypto.investment-plays' entry/exit logic; distinct from oracle.volatility-monitor's real-time (not historical) read.

## Output

Returns a JSON object with a 'summary' string describing the overall historical pattern analysis and a 'findings' array listing specific identified patterns, signals, or structural observations derived from the asset's historical data. The response is labeled as a BlindOracle deliverable with the oracle.historical-analysis SKU.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "prompt": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "schema": {
  "type": "object",
  "properties": {
   "summary": {
    "type": "string"
   },
   "findings": {
    "type": "array",
    "items": {
     "type": "string"
    }
   }
  }
 },
 "example": {
  "summary": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blindoracle-historical-analysis-8e485717/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.craigmbrown.com](https://www.zero.xyz/host/api.craigmbrown.com/llms.txt)