Skip to main content

Coverage and discovery

The Tauric API serves these data families, each with its own page. Every instrument has one instrument key, which you find by searching.

Routes​

taskroute
list every served dataset, with its coverage, depth, units, and limitationsGET /v1/datasets
read one dataset's recordGET /v1/datasets/{dataset}
search or list instruments of any kindGET /v1/instruments
one instrument's identity, classification, and datasetsGET /v1/instruments/{key}
search or list seriesGET /v1/series
the classification vocabularyGET /v1/taxonomy
the sector, industry group, industry, and sub-industry listsGET /v1/taxonomy/gics/sectors, /industry-groups, /industries, /sub-industries

Coverage by family​

Coverage is per capability: a listing can have quotes and bars and no financials. GET /v1/datasets and GET /v1/instruments/{key} give the current coverage.

familywhat is servedroutesdiscover
batch quotes and market viewsbatch quotes; equity indices, sectors, and movers; rates and credit; fixed-income ETFs; the macro snapshot; cross-asset; commodities; FX; crypto/v1/quotes, /v1/markets/…/v1/datasets
stocks and ETFsUS-listed stocks, ETFs, and depositary receipts: quote, daily and intraday bars, technicals; profile, analyst consensus, earnings and dividend calendar, corporate actions/v1/securities/{symbol}/…/v1/instruments?kind=security&dataset=securities.quote
filings and financialsthe SEC filings index and financial-statement facts as filed, point in time; Form 4 insider transactions and Form 13F institutional holdings/v1/securities/{symbol}/filings, /financials, /insider-transactions, /institutional-holders/v1/instruments?kind=security&dataset=securities.financials
economic and market serieseconomic statistics, index levels, volatility, physical supply and demand/v1/series/{key}/…/v1/series (filters, q)
rates, credit, and volatilitythe yield curve and rates, credit spreads, the macro snapshot, the VIX term structure/v1/markets/rates/…, /v1/markets/credit/spreads, /v1/markets/macro/snapshot, /v1/series/…/v1/datasets
futurescontract families, their continuous front-month series (quote, bars, technicals), Commitments of Traders, commodity supply and demand/v1/futures/…, /v1/markets/commodity/…/v1/instruments?kind=future
FXthe 28 served G10 pairs: spot quote, daily open/high/low, daily reference rates/v1/fx/{pair}/…, /v1/markets/fx/pairs/v1/instruments?kind=fx
cryptoexchange spot pairs (quote, daily bars), crypto asset profiles, the top-100 asset list/v1/crypto/pairs/{pair}/…, /v1/crypto/assets/{asset}, /v1/markets/crypto/…/v1/instruments?kind=crypto
news and eventsarticles with their annotations, and semantic search; events extracted from articles/v1/news…, /v1/securities/{symbol}/events/v1/news?instrument=…
digests, theses, and themesTauric AI analysis/v1/digests/market, /v1/digests/{digest_id}, /v1/securities/{symbol}/digest, /thesis, /v1/theses, /v1/themes/v1/datasets

Tauric AI (research, the copilot, model inference) has its own pages.

Outside coverage, or where a value is not held, the answer is an error code for a whole answer, or a null field (missing values).

The served universe​

The securities served are a set of US listings. GET /v1/instruments?kind=security&dataset=securities.quote lists them. A registered listing outside them gets 404 not_supported; a ticker that names no registered listing gets 404 not_registered.

Find an instrument​

Every instrument has one key, such as security:AAPL or fx:EURUSD (instrument keys). Search, then use the key the search returns:

bash
curl "https://api.tauric.ai/v1/series?q=10-year%20treasury" \
-H "Authorization: Bearer $TAURIC_API_KEY"
curl "https://api.tauric.ai/v1/instruments?q=EUR/USD" \
-H "Authorization: Bearer $TAURIC_API_KEY"
curl "https://api.tauric.ai/v1/instruments?q=future:XCME:ES" \
-H "Authorization: Bearer $TAURIC_API_KEY"
curl "https://api.tauric.ai/v1/instruments/security:AAPL" \
-H "Authorization: Bearer $TAURIC_API_KEY"

/v1/instruments searches every kind; /v1/series searches only series, with the same matching and ordering. Python examples shows the search from Python.

Query matching​

q matches:

  • a key: the full key with its kind (series:…, future:XCME:ES) or its segment, but not the kind word alone;
  • a ticker;
  • a name;
  • an everyday name (PCE_PRICE_INDEX finds the PCE price index);
  • an exchange or index code.

A one-word query matches the start of a key token or of a word in a name (cpi, vix), never the middle of one (es does not find jobless). A query of several words returns only rows where every word matches: corn ending stocks finds "U.S. Corn: Ending Stocks".

Result order​

An exact match of a key, a ticker, or a familiar code ranks first. Ties go by kind: security, future, FX, crypto, series (BTC lists the bitcoin futures before crypto:BTC-USDT).

Current and historical listings​

By default (coverage=current) GET /v1/instruments lists and searches the served listings. A delisted listing stays readable, but the default list and q leave it out. coverage=all adds delisted listings and registered listings that are not served; each row states listing.state (listed or delisted) (listing lifecycle). coverage changes only securities and crypto pairs.

Look up one instrument​

GET /v1/instruments/{key} answers an instrument's kind, name, identity, classification, and datasets, delisted listings included (identifiers). An unregistered key answers 404 not_registered.

Series lists and the taxonomy​

GET /v1/series lists every served series with its series block (series values). Filter it with instrument_type, asset_class, asset_subclass, and category.

GET /v1/taxonomy lists the classification vocabulary (asset_class, instrument_type, object_kind) and the content-tag vocabularies (exposure, content_domain) that news filters on (asset class and instrument type).

Sector and industry lists​

Sectors and industries follow the GICS hierarchy: sector, industry group, industry, sub-industry. GET /v1/taxonomy/gics/sectors, /industry-groups, /industries, and /sub-industries list the four levels; a company's place in them is on stocks and ETFs. Each list below the sector level filters by its parent levels: ?sector=, ?industry_group=, ?industry=, each taking a key of the level named; anything else is 422.

A sector's proxy_etf (security:XLK) is the ETF the market sector views measure it by.

The dataset catalog​

GET /v1/datasets/{dataset} reads one dataset's record. GET /v1/datasets lists the catalog in pages of complete records: limit (default 10, at most 25) and after page it (lists). For one instrument, read the datasets of GET /v1/instruments/{key}. Every field is described in the API reference.

Read these before you rely on a dataset:

  • values.unavailable_fields: the fields null on every answer, with their reason (fx.history names close, so FX bars carry no close).
  • operations: the routes that serve the dataset, each with its operation name (also its MCP tool's name), method, path, and example.
  • point_in_time.operations: the paths that take known_at; when it is empty, known_at is 422.
  • limitations: what the dataset does not say, each with the reason codes a response carries for it.