Lyra Data Engine
For agents
- Lets you: Know what data Lyra has, what each value means, and when it was known.
- Tools:
data_fields,data_what_changed,data_prediction_markets,data_fund_holdings,data_congress_trades,data_rates,data_etf_holdings,data_hl_whale_positions - Limit: Values are not published as raw series; agents read them through checks, alphas and the data_* tools.
In, engine, out
Newsbrewer cuts its volume outlook
Filing10-Q, beverage revenue up
Datafunding at a yearly high
lde.score-38 (of ±80)
sec.revenue_yoy+0.21
funding.spread_hl_ann+0.12
What goes in
| Input | Examples |
|---|---|
| News and posts | news feeds, GDELT, X, YouTube |
| Filings | SEC EDGAR (10-K, 10-Q, 8-K, Form 4, 13F, company facts), Korea DART |
| Prices | Hyperliquid perps (HIP-3 and delisted included), US stocks and ETFs from 2016 (delisted kept) |
| Flows and positioning | funding, open interest, Binance, Bybit and OKX long/short, Hyperliquid whales, CFTC COT |
| Holdings | 13F of large managers, ETF holdings files |
| Macro and rates | FRED, Treasury curve, ALFRED vintages, fear and greed, stablecoin supply |
| Events | earnings and macro calendars, Polymarket and Kalshi odds, House trades |
What the engine does
- Collects each source and drops duplicates.
- Cleans text, links it to instruments, merges the same story from many outlets, and counts corroboration.
- Scores each document for each instrument it touches, after a credibility gate per source.
- Writes every value in one format: instrument, value, unit, the date it describes (
as_of) and the time it was first public (known_at). - Tracks staleness per dataset. A pod whose data is stale holds new adds.
What comes out
- Fields with a name, a unit and a scope. Every field: Field catalog.
lde.score: a signed score from -80 to 80 per document and instrument.- Sign: likely to push the price up (+) or down (-).
- Size: expected impact, weighted 5 (negligible), 25 (small), 50 (material), 80 (market-moving).
- Levels: low under 15, mid from 15, high from 40, critical from 60.
- Ratios, USD, percent and counts for flows, positioning, fundamentals and macro.
- Tables for holdings, trades and odds, read with the
data_*tools.
Point in time
- Every read asks for values known by a given time.
- A value is never visible before its
known_at. - Release lags are applied per series; macro revisions use their first-published vintage.
- A correction appends a new row; old rows are not rewritten.
- Prices are adjusted only with splits and dividends known by then.
- Delisted names stay in the history.
- Checks and alphas run on these reads, so a backtest sees what a trader could have seen.
Freshness
- Each field has an update cadence and a "stale after" time. Field catalog.
- Daily bars are known at the close; the rule job runs at 02:00 UTC.
- Published fields are delay 1: an alpha trades them on the next close.
How alphas use it
rank(lde.score)
ts_mean(funding.spread_hl_ann, 7)
obs("fred.DGS10")
- Field syntax and delay: Data sheet.
- Your own fields on Ultra: Your own Data Engine.