The rest of the shelf: options, currencies, commodities, news, discovery, and the Marketplace

Why this matters. This is where "do you have X?" gets answered, and the honest answer is more often yes than people here expect. Foundation: Which instrument does what?

Everything that is neither a listed price nor a company filing.

Instruments beyond equities

Currencies and crypto come through the same price endpoints as everything else, which surprises people: a forex pair or a crypto ticker is a symbol like any other. US options with greeks come through the Marketplace. Commodities cover oil, gas, metals and agriculture. Real estate carries price series by country and region. CBOE Europe indices are there in beta.

News, and what it is worth

News aggregated from major sources, sentiment scored on top of it by language models, and word weights underneath that. Clients build news tabs, market-mood widgets and event-driven signals on it. The public curriculum is blunt about the limits of that idea, which is worth knowing before you sell it: which news actually moves prices.

Finding things

Two families that are easy to forget and answer a surprising share of questions:

• Discovery — a screener over the whole universe, and technical indicators computed for you rather than in the client's code.
• Reference data — search, the exchange and symbol lists, trading hours and holidays, symbol change history for tickers that were renamed, identifier mapping between CUSIP, ISIN, FIGI, LEI, CIK and our symbols, and forty thousand company logos.

Identifier mapping deserves the emphasis. An institutional client whose universe is keyed by ISIN is not going to rekey it by hand, and this endpoint is often the whole answer to whether an integration is possible at all.

Sanctions

OFAC and other screening lists: entities, vessels, programs and sources. A compliance question rather than a market one, and it is on the shelf.

The Marketplace, precisely

The Marketplace is where partners sell datasets through us: ESG scores, options, index constituents, bond and equity analytics. One API, one integration, one place to look, and someone else's data.

Two facts about it are worth more than any list of fields:

1. Entitlement is separate. A standard token that works everywhere else gets a 403 here. When a client reports that "the API is broken" on a marketplace path, this is the first thing to check.
2. The vendor documents it, not us. Some marketplace products have no page on our documentation site at all. "We sell it, the vendor documents it, here is who to ask" is a complete and honest answer. Inventing a link is not.

Try it now

Take three requests you would have guessed we cannot serve. Find the family each would live in, then check — the honest answer here is more often yes than people expect, and checking is the only way to find out.

1. Start with the two families everyone forgets, because they answer a surprising share of questions. Discovery: /screener?filters=[["sector","=","Technology"]] and /technical/{ticker}?function=sma&period=50, which computes indicators for the client rather than making them write the loop — function is required, and without it the call is a 422 rather than a default. Reference data: /search/{query}, /symbol-change-history, /exchange-symbol-list/{exchangeCode}. The screener's answer and the moving average's are below.

2. Look at the one that decides whole integrations. /id-mapping?filter[isin]={isin} translates between CUSIP, ISIN, FIGI, LEI, CIK and our symbols — the filter is what makes it a call. An institutional client whose universe is keyed by ISIN is not going to rekey it by hand, so this single path is often the entire answer to whether the work is possible at all. Apple's ISIN is below, and then the same endpoint filtered by our symbol: only the primary US line carries the CUSIP, FIGI and CIK.

3. Try the corners: /commodities/historical/BRENT, /real-estate/countries, /news?s={ticker}&limit=10, /sanctions/entities. Currencies and crypto need no special path — a forex pair or a crypto ticker goes through /eod/{ticker} like any other symbol, which is the fact that surprises people most. Two of the corners answer below.

4. Now the wall. A marketplace path without the entitlement answers 403, and the body is an HTML error page, not JSON — so a client whose code calls resp.json() on it sees a parse error, not a status. Measured on 28 September 2026 with the public demo token, which covers six symbols:

   Request	Status	Content-Type	Body
   /mp/unicornbay/options/contracts?filter[underlying_symbol]=AAPL	200	application/json	the chain
   /mp/unicornbay/options/contracts?filter[underlying_symbol]=NVDA	403	text/html	a page titled "Forbidden"

   A 403 here is entitlement, not breakage — and it is the first thing to check when a client reports that "the API is broken" on a marketplace path.

5. Note which of your three guesses you got wrong. That is the part of the shelf you do not know yet. And where a marketplace product has no page on our documentation site, "we sell it, the vendor documents it, here is who to ask" is a complete and honest answer. Inventing a link is not.