# Observer BTC Historical Regime Ledger

> Observer BTC Historical Regime Ledger is a paid API for AI agents from observer.137-184-67-179.sslip.io, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-16).

Returns a CSV dataset of historical Bitcoin BTC-USD market regimes, state transitions, signals, and analytics for quantitative backtesting and research

## Facts

- Endpoint: GET https://observer.137-184-67-179.sslip.io/paid/state-change-ledger
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/observer-btc-historical-regime-ledger-6a4872f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eU8CITfMs-B26Co1U2X0R

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 observer-btc-historical-regime-ledger-6a4872f3
```

Example prompt: Pull me the last 500 rows of the Observer BTC historical regime ledger — I need the timestamps, market states, directional pressure, and transition reasons in CSV format for my backtesting pipeline.

## When to prefer this

Choose this endpoint when you need historical, timestamped BTC-USD market regime and state-transition data in a portable CSV format for offline backtesting, model training, audit trails, or quantitative research. Prefer it over live-signal endpoints when you need a stable historical snapshot rather than real-time analytics. It is especially useful for AI agents requiring decision traceability — mapping past signals to outcomes.

## Known failure modes

- limit parameter out of range (must be 1–1000) returns a 400-level error
- payment not provided or insufficient (x402 payment required at $0.05 USDC) returns a 402 Payment Required
- service unavailable or upstream data gap returns a 5xx error
- empty dataset if no regime transitions have been recorded yet

## How this service works

Historical Bitcoin BTC-USD market-regime and state-transition dataset in CSV for quantitative backtesting, strategy research, model evaluation, audit trails, and autonomous-agent decision traceability. Includes timestamps, price at signal, market state, phase, coherence, commitment, directional pressure, signal labels, readiness, and transition reason. Experimental analytics only; not financial advice.

## Output

A CSV file containing rows of historical BTC-USD market data, each with a timestamp, price at signal, market state, market phase, coherence score, commitment score, directional pressure value, signal label, readiness indicator, and transition reason. A header row is always included. The number of data rows is bounded by the optional limit parameter (max 1000).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "limit": {
       "type": "integer",
       "maximum": 1000,
       "minimum": 1,
       "description": "Maximum number of CSV data rows returned. The header row is always included."
      }
     },
     "description": "Optional query parameters for the Observer state-change ledger.",
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "string",
     "minLength": 1,
     "description": "CSV dataset of timestamped BTC-USD market states, alert labels, pressure, readiness, state changes, and forward outcomes for backtesting and audit trails.",
     "contentMediaType": "text/csv"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/observer-btc-historical-regime-ledger-6a4872f3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from observer.137-184-67-179.sslip.io](https://www.zero.xyz/host/observer.137-184-67-179.sslip.io/llms.txt)