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. Respect vintages. Default financials are latest-restated; as_reported exists for “what did they originally say”. Macro is point-in-time.
  3. Missing is not zero. Null means unavailable. Say so.
  4. Honour the headers. Retry-After on 429; watch RateLimit-Remaining and X-Quota-Remaining instead of discovering limits by hitting them.
  5. No advice. Present data; do not recommend trades. The site’s terms apply to anything you relay.
  6. 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

No MCP server is published yet; /.well-known/mcp.json says so and points at the HTTP API. When it ships, the manifest will gain a servers entry at the same URL.