EODHD: The Product checkpoint — what we sell, every way in, and how to find it

Course capstone. Four units ago "EODHD" was a company name and "the API" was a single door. It is now a shelf with named families on it, four ways in, a documentation hierarchy you can walk, and a routing habit for questions that arrive with the wrong words.

The course in one architecture

• What we are — a market-data company, with a precise meaning of "market data" and a list of what we are not; the people who reach for this data and what they are trying to do; and where the data actually comes from, which is the answer to half the questions about it (Unit 1).
• What we sell — prices at every speed from end-of-day to real time; the company's own numbers: fundamentals, corporate actions, calendars; the wider economy: macro, rates and credit; and the rest of the shelf: options, currencies, commodities, news, discovery (Unit 2).
• Every way in — the API is one door of several; the SDKs, what exists and what each one is; reaching the data without writing code; and the client that is an assistant: the MCP server and the Claude skill (Unit 3).
• Finding it later — the hierarchy of sources; the vocabulary that makes search work: symbols, dates, identifiers; the thirteen endpoint families as a map of the surface; and which endpoint answers which market question (Unit 4).

The sentence, decoded

"A client wants live prices for European stocks in a spreadsheet, and asks whether we have ESG scores." Run it through the instruments. Live prices — a speed, with a family and a plan behind it (Unit 2). European stocks — an exchange code in the ticker, and the vocabulary that makes the search work (Unit 4). In a spreadsheet — a way in without code (Unit 3). ESG scores — a marketplace dataset with its own terms, and a question to route rather than answer from memory (Unit 2, Unit 4). One request, four units, and the reply is a set of correct pointers rather than a guess.

Where this connects

The Market Data domain is this course's shelf taken product by product, with the calls made and the responses read; its API foundations course is the first place to send anyone who finished here and wants to make a request. The reference page at /academy/reference is unit 4's map, kept current. And the routing habit — name the family before naming the endpoint, and send a question elsewhere when it belongs elsewhere — is the one thing this course asks you to keep after the exam.

Checkpoint

The exam ahead draws on all four units. The bar: a real request in the words a client uses, and the ability to name the family, the way in, and the page — or to say correctly that it is not a product question.

Before you sit it

Each of these is a minute at your desk. Any one that is not names the lesson to reopen first.

• Say what "market data" means here and name two things we are not — What "market data" means here, and what we are not
• Name the three speeds of price data and what separates them — Prices: end of day, intraday, real time
• List the ways in besides the API, and say who each one is for — The API is one door of several
• Take a market question in a client's words and name the endpoint family that answers it — Which endpoint answers which market question

Try it now

1. Write the one-sentence version of each unit from memory — four sentences, your pocket card. Do this before opening anything.
2. Then run the routing habit on the shelf itself. /exchanges-list?fmt=json returns every exchange we cover with its code; eight of its rows are below. Pick three from three continents and, for each, name the family a client would need for daily prices, for the company's accounts, and for the calendar of its next earnings date — without opening the documentation.

3. Check yourself against /academy/reference, and count how many you named correctly. Then take the last five real requests you handled and do the same. If the count is five, sit the exam; if not, unit 4 is the one to reopen.