Skip to content

Coverage

What Argus can answer about a security depends on its tier. The tiers are stated in config/consumer_coverage.yaml, and the argus://coverage resource returns them to every connected AI app. Nothing is real time.

Tiers

  • Every listed company: the filed financial facts of every US-listed company in the SEC company ticker list, read from the SEC nightly bulk archive (financials, since release 1.1.39).
  • On the first request: the filings, company events, corporate actions and insider and ownership reports of a listed company (company_data_on_request), and the end-of-day prices and split history of a listed stock or exchange-traded fund (prices_on_request), both since release 1.1.39. A first capture takes about a minute. The security is then refreshed daily while it is in use: while someone has asked about it in the last 90 days, or an active account holds it, watches it or has an alert on it. A security that leaves use keeps its data, and the next request captures what is missing.
  • Ahead of any request: the companies, spot crypto trusts and funds of the lists stocks and funds, captured by fixed jobs. Fund facts cover only the funds of this list.

The coverage resource, first captures and identity

  • The argus://coverage resource returns the lists as covered_symbols, the switches as market with a statement, and coverage_version and generated_at. Since release 1.1.40 covered_symbols.crypto lists the crypto pairs (24 since release 1.1.43), and crypto says what they get; while the crypto list is empty neither key is present. Since release 1.1.41 covered_symbols.trusts names the US-listed spot crypto trusts behind the crypto list apart from the companies in covered_symbols.stocks, and securities counts them apart: a trust is never counted as a company. While the list names no trust the key is absent.
  • While the first capture of a security runs, a tool waits up to ten seconds; if the data is not ready it answers temporarily_unavailable with retry_after_s: 20 and says the security is being captured for the first time. A security whose capture found nothing answers as before: not_covered for prices, empty for filings and events. get_overview, which puts several kinds of data together, answers with what it has and a first_capture note. Over the daily cap of first captures, per account or for the whole service, a tool answers quota_exceeded with retry_after_s: 3600.
  • A tool that takes a symbol answers not_covered for a symbol whose data Argus does not offer. find_security answers empty with a not_covered note. Neither says the security does not exist.
  • Identity is a second, wider layer. Once a whole copy of the SEC company ticker list has been captured, find_security also names the tickers of that list. Once the SEC fund ticker list has been captured as well, it names the exchange-traded funds of that list whose newest annual report on Form N-CEN, or whose newest shareholder report on Form N-CSR or N-CSRS, states a listing on a US exchange under that ticker, by the name of their registrant, the trust or company that files the reports (IVV: iShares Trust). Such a fund gets its end-of-day prices and split history on the first request; its filings are not captured and it has no fund facts. A mutual fund share class, or a fund without such a report, is not named. Every candidate carries coverage: full for a symbol of the coverage lists, on_request for a listed security the market switches give data (an operating company with a CIK while financials or company_data_on_request is on; a priced type while prices_on_request is on), with an on_request note, and identity_only otherwise. An identity_only candidate has a name, a ticker and a CIK, and no financials, filings, events or prices; the answer says so in an identity_only note. The SEC list also names securities traded over the counter and states no venue that Argus can cite, so an identity_only candidate has exchange: null and the note says that the list names such securities too.
  • A ticker is not_found only when every list copy on file (the company ticker list, and the fund ticker list once captured) is at most three days old and none names it. find_security then answers empty with a not_found note, and a tool that takes a symbol answers the not_found error. The SEC lists leave out some listed securities, for example a fund that is a series of a trust and has no report stating its listing yet, so the wording is "the SEC company ticker list does not name it".
  • A name search returns at most 50 matches from the identity layer. When more exist, the answer says that more are available.
  • partial and the "sources were incomplete" note mean that something the answer should contain is missing. Fields that no source available to personal accounts states, such as the first listing date, do not make an answer partial; they are null.

Crypto assets

  • Argus covers 24 crypto assets themselves, written as pairs (requirements 3.1): BTC-USD, ETH-USD, AVAX-USD, BNB-USD, DOGE-USD, HYPE-USD, LINK-USD, LTC-USD, NEAR-USD, SOL-USD, SUI-USD, TRX-USD, XRP-USD, ZEC-USD, BCH-USD, TAO-USD, XLM-USD, ADA-USD, DAI-USD, LEO-USD, USDE-USD, XMR-USD, USDC-USD and USDT-USD. Release 1.1.40 listed the first two and release 1.1.41 the next twelve and the last two. The list follows a published rule (ADR 0024): Bitcoin and Ethereum, then the assets that US-listed spot trusts hold, then those among the 50 largest by CoinMarketCap market value that US over-the-counter trusts hold (BCH, TAO and XLM), then those among the 20 largest (ADA, DAI, LEO, USDE and XMR), then the two main US-dollar stablecoins issued on Ethereum. The order is never a ranking and no answer states a rank. The coverage list names each US-listed trust as an exchange-traded trust; the over-the-counter trusts are not on it.
  • A bare code such as BTC or XRP is read as a ticker of a listed security, never as the asset; when it is one (XRP is the Bitwise XRP ETF), a crypto_pair note points to the pair. A listed security that holds crypto, such as a spot trust, stays a security.
  • The value of a day is the last quote of that UTC day, at 23:55 UTC, from CoinMarketCap. Argus stores it as the UTC daily bar of that day and shows it as close; it is never called the source's daily close. CoinMarketCap states no open, high, low or volume here, so they are null with a close_only note. freshness.mode is daily_close_utc. Nothing is real time.
  • Every source of such a quote carries the attribution Data from CoinMarketCap.com and the link https://coinmarketcap.com/. get_sources adds methodology, the page where CoinMarketCap explains how it computes its quotes.
  • get_quote reads the past 14 UTC days. Its summary states the quote in cents, for example "BTC-USD (Bitcoin): the last quote of 2026-11-14 (UTC, 23:55) was 64,145.95 USD according to CoinMarketCap; not real time."; data.close keeps every digit the source gave. previous_close is the day before, and change and change_percent are computed from the two quotes. A day that has ended but whose quote is not stored yet gives a not_available_yet note; a quote more than three days old makes the answer partial. There is no 52-week range.
  • get_price_history has a row for every UTC day, weekends included. A week runs Monday to Sunday in UTC. A crypto asset has no splits, so adjustment: split_adjusted is invalid_input. Asked for days before the first one stored, the answer carries a source_history_limit note: CoinMarketCap's Basic plan reaches back one year.
  • record_holdings takes quantities in units, up to 8 decimals. A holding without a past date is recorded as of the end of the latest UTC day, at 00:00 UTC. get_portfolio values it at the last quote of the latest UTC day on file, within the 3 days before the valuation time (no_recent_utc_close otherwise), and only while the pair names the same asset as when it was recorded (identity_changed otherwise).
  • get_overview gives the asset's identity and says what Argus offers for it. Financial statements, filings, changes, events and alerts are not offered for a crypto asset; those tools answer not_covered and say so.