# BlindOracle Alert Generator

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

Defines a custom price or event alert and returns its current trigger state (armed, fired, or stale) based on oracle price and volatility feeds.

## Facts

- Endpoint: POST https://api.craigmbrown.com/v1/services/oracle.alert-generator
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blindoracle-alert-generator-1d6b5f14
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BnnovxeYzGEFiuB-Hz4I3

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-alert-generator-1d6b5f14 -d '<json body>'
```

Example prompt: Set up a price alert for BTC/USD that fires when it crosses $70,000, and tell me whether it's currently armed, fired, or stale based on the latest oracle data.

## When to prefer this

Choose this endpoint when you need to define a conditional price or volatility alert and immediately know its current trigger state — not just raw price data. It is the trigger layer on top of the oracle.price-feed and oracle.volatility-monitor data layers. Prefer it over raw price feeds when you need stateful alert evaluation with settlement proof, especially for automated trading workflows or agent decision trees that must act only when a condition is met.

## Known failure modes

- Invalid alert specification or malformed prompt input returns an error
- Oracle data unavailable results in a stale state or timeout
- Ambiguous or missing threshold values cause evaluation failure
- Price or volatility feed outage may delay trigger evaluation
- Insufficient payment (x402 protocol) results in 402 Payment Required response

## How this service works

Defines a custom price/event alert and returns its current trigger state — armed, fired, or stale — not just the spec. Settlement proof: ProofOfSettledOutcome (kind 30120, data/proof_settled_outcomes.jsonl). Reads off oracle.volatility-monitor and oracle.price-feed; this SKU is the trigger layer, not the data layer.

## Output

Returns the alert definition along with its current trigger state: armed (condition not yet met), fired (condition has been met), or stale (condition is outdated or data is too old). Includes a settlement proof (ProofOfSettledOutcome, Nostr kind 30120) and references the oracle feeds (price-feed and volatility-monitor) used to evaluate the trigger.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "pair": {
   "type": "string"
  },
  "task": {
   "type": "string"
  },
  "condition": {
   "enum": [
    "above",
    "below"
   ],
   "type": "string"
  },
  "threshold": {
   "type": "number"
  }
 }
}
```

## 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-alert-generator-1d6b5f14/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)