# BlindOracle Volatility Monitor

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

Returns a real-time volatility reading for a specified trading pair with configurable alert thresholds for actionable signals.

## Facts

- Endpoint: POST https://api.craigmbrown.com/v1/services/oracle.volatility-monitor
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blindoracle-volatility-monitor-b8eb0d76
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xv67DXNCNCGlk3H_FM0QN

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-volatility-monitor-b8eb0d76 -d '<json body>'
```

Example prompt: What's the current volatility on BTC/USD — and let me know if it's crossed a high-risk threshold I should act on?

## When to prefer this

Choose this endpoint when you need a real-time, single-call volatility reading for a specific trading pair with threshold-based alerting built in. Prefer it over historical-analysis when you need the current number rather than trend explanation, and over alert-generator when you want the volatility value and alert state in a single response rather than just firing a notification.

## Known failure modes

- Invalid or unrecognized trading pair returns an error or empty findings
- Malformed prompt input may return a generic or unhelpful summary
- Upstream market data unavailability causes stale or failed reads
- Exceeding rate limits or insufficient USDC balance (at $0.04/call) causes payment failure
- Settlement proof missing if oracle backend is degraded

## How this service works

Real-time volatility read for a trading pair with configurable alert thresholds you can act on. Settlement proof: ProofOfSettledOutcome (kind 30120, data/proof_settled_outcomes.jsonl). Complements oracle.alert-generator (fires the alert) and oracle.historical-analysis (explains the trend behind the number).

## Output

Returns a JSON object with a 'summary' string describing the current volatility state and a 'findings' array listing key observations. Also includes metadata such as the SKU ID, service name (Volatility Monitor), powered-by attribution (BlindOracle), and a settlement proof (ProofOfSettledOutcome) confirming the read was completed.

## 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-volatility-monitor-b8eb0d76/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)