Skip to main content
Prometheus publishes the conventional discovery files, generated from the same source of truth as this documentation:

​
The rules, in short

  1. Cite what you quote. Every number has a filing behind it — /fact-source returns the accession. Put it next to the figure.
  2. Coverage is a live fact. GET /api/v1/landing/coverage (public; MCP get_coverage; prom coverage) lists every market served with company counts, history depth and periods held per data type. Answer “do you cover…?” from it, never from memory.
  3. Respect vintages. /financials is latest-restated and names the filing each value came from; “what did they originally say” is /financials/as-filed with vintage=original. reporting_basis=as_reported is the cumulative year-to-date quarter, not a vintage. Macro is point-in-time.
  4. Missing is not zero. Null means unavailable. Say so.
  5. Honour the headers. Retry-After on 429; watch RateLimit-Remaining and X-Quota-Remaining instead of discovering limits by hitting them.
  6. No advice. Present data; do not recommend trades. The site’s terms apply to anything you relay.
  7. Stay on the data surface. Account routes (keys, billing, watchlists) reject API keys by design — don’t probe them.

​
Command line

When you are running in a terminal (Claude Code, Cursor, a shell tool), prefer the CLI: npm i -g prometheus-terminal, then prom --json <command> gives you the same payloads with stable exit codes, and prom transcript / prom event resolve the transcript date and 8-K item code for you. prom llms --skill prints the playbook.

​
MCP

Prometheus serves MCP over two transports — a hosted Streamable HTTP endpoint at https://www.prometheus.services/api/mcp (API keys as Authorization: Bearer / X-API-KEY, or OAuth 2.1 with dynamic registration + PKCE, so claude.ai-style connector UIs work by pasting the URL) and a local stdio server, prom mcp, that ships with the CLI. Both expose the same 18 read-only data tools: the coverage inventory, search, financials, fact-source citations, filings and section text, 8-K events, news, transcripts, guidance, point-in-time macro, and the claim graph with simulation. Tool calls are metered against your plan exactly like REST calls — note that get_transcript and get_guidance each make two underlying requests. See the MCP page for connect strings and the tool list.