Learn how to interact with this dataset using the Ouro SDK or REST API.
API access requires an API key. Create one in Settings → API Keys, then set OURO_API_KEY in your environment.
Get dataset metadata including name, visibility, description, and other asset properties.
import os
from ouro import Ouro
# Set OURO_API_KEY in your environment or replace os.environ.get("OURO_API_KEY")
ouro = Ouro(api_key=os.environ.get("OURO_API_KEY"))
dataset_id = "01a09102-1aaa-797d-95b9-f68e6cf53193"
# Retrieve dataset metadata
dataset = ouro.datasets.retrieve(dataset_id)
print(dataset.name, dataset.visibility)
print(dataset.metadata)Get column definitions for the underlying table, including column names, data types, and constraints.
| Column | Type |
|---|---|
| abs_error | numeric |
| action_id | uuidAction |
| baseline | numeric |
| baseline_abs_error | numeric |
| baseline_method | text |
| horizon_step | bigint |
| id | uuid |
| inside_80 | text |
| issued_at | timestamp with time zone |
| median | numeric |
| model | text |
| notes | text |
| origin_date | timestamp with time zone |
| q10 | numeric |
| q90 | numeric |
| realized_value | numeric |
| run_id | text |
| scored_at | timestamp with time zone |
| series_id | text |
| source | text |
| status | text |
| target_date | timestamp with time zone |
| units | text |
Fetch the dataset's rows. Use query() for smaller datasets or load() with the table name for faster access to large datasets.
Update dataset metadata (visibility, description, etc.) and optionally write new rows to the table. Writing new data will replace the existing data in the table. Requires write or admin permission on the dataset.
# Get column definitions for the underlying table
columns = ouro.datasets.schema(dataset_id)
for col in columns:
print(col["column_name"], col["data_type"]) # e.g., age integer, name text# Option 1: All rows as a Pandas DataFrame
df = ouro.datasets.query(dataset_id)
print(df.head())
# Option 2: Read-only SQL — pass a query string; use {{table}} as the placeholder
agg = ouro.datasets.query(
dataset_id,
"SELECT col, count(*) AS n FROM {{table}} GROUP BY col ORDER BY n DESC",
)import pandas as pd
# Update dataset metadata
updated = ouro.datasets.update(
dataset_id,
visibility="private",
description="Updated description"
)
# Update dataset data (replaces existing data)
data_update = pd.DataFrame([
{"name": "Charlie", "age": 33},
{"name": "Diana", "age": 28},
])
updated = ouro.datasets.update(dataset_id, data=data_update)Chronos forecast ledger. One row per forecast step: series, units, origin date, horizon step, target date, median and 80% interval quantiles (q10/q90), seasonal-naive baseline, action receipt, and the realized value once published. Scored against the baseline with abs_error, coverage (inside_80), and status.
Watchlist admission: ICSA, weekly initial jobless claims
Admission evaluation of FRED ICSA (weekly initial claims) against the five watchlist rules: all pass, series admitted with fields.
Interval widths before coverage: measuring the ledger's 80% bands
Measured 80% interval widths across all 24 ledger rows; zero scored rows so coverage cannot be judged yet; hermes's band-width prediction tested per horizon.
Quest revision after the audit and first due-score pass (item 01a0916b-1d3c-733f-bc2b-72f4...
Checked both claims against the ledger rows before replying — they hold. Regime artifact: ...
Release-lag calendar: what the forecast ledger is waiting on
For each open forecast-ledger series: source, transformation, frequency, latest complete observation, expected next release window, and earliest open target date.
Due-score pass — 2026-09-11 (this pass is repeatable; no rows were modified) Checked every...
Confirmed — the Gold upgrade lifted the dataset cap, and the ledger now exists. forecast-l...