aether-research

Aether equity research

You have access to Aether — a search engine built for agents over SEC filings, earnings-call transcripts, and EU financial regulation. Every hit returns the exact primary-source passage, an accession-numbered citation, and a sec.gov / EUR-Lex URL. Your job: use it so every factual claim in your answer traces to a filed document.

Rule one: name the company, then narrow

Every company tool takes an issuer — {ticker}, {cik}, or {company_name} for non-US filers with no US ticker. Put the company in issuer and the question in query:

{"query": "data center revenue growth drivers", "issuer": {"ticker": "NVDA"}, "fiscal_year": 2027}

Not {"query": "NVDA data center revenue growth drivers"}. Both appear to work, which is what makes the second one dangerous: with no issuer the engine guesses the filer from your query text, and generic words that happen to be tickers point it at the wrong company. Measured: the ordinary word "customers" resolves to Customers Bancorp, which then took two ranks of an NVIDIA memo.

Then read two fields off every response before you use it:

• scope — "issuer" or "cross_company".
• quality_caveat — present when the answer is not issuer-precise.

scope: "issuer" with no caveat is the only guarantee you got a filtered answer. A caveat arriving with scope: "issuer" means the engine guessed the company and names its guess — check it is the one you meant. A cross_company answer spans every filer and is ranked by relevance only: say so in your write-up rather than presenting it as a complete list.

Use scope: "cross_company" deliberately, for questions genuinely about many issuers ("which filers name NVIDIA as a supplier"), and budget up to 15 s for it. Then re-run scoped on any company worth a closer look.

Rule two: if you know the document, don't rank it

query is optional. Omit it and you get fetch mode: pass an identifier (issuer.ticker / issuer.cik / issuer.company_name / accession_number) plus any of form_type / fiscal_year / section / quarter, and the filing comes back in filing order — newest first, then document order, so Item 1 precedes Item 1A precedes Item 2. No ranking, tens of milliseconds, mode: "fetch", and no confidence field because nothing was scored.