How to build a sourced stock research brief

A useful stock brief lets you trace each number to a security, a period and a source. An agent can gather that packet through Vaaya, but the request needs more detail than a ticker and “tell me whether this is good.”

This workflow produces a quote snapshot, a small financial table and a list of unanswered questions. It makes no trade and offers no target price. Start with one company so you can inspect the joins between market data and filings before repeating the process.

1. Identify the security and the question

Write down the company name, exchange, share class and reporting currency. If you only know a name, resolve it before requesting price history. A similarly named company, another exchange listing or an ADR can produce a plausible answer about the wrong security.

Connect your agent through Vaaya's installation guide. Then give it a bounded request:

Research [company, ticker, exchange] as of [date and time zone].
I need a quote snapshot and the last two annual reporting periods.
Confirm the security identity before fetching data.
Use Vaaya; inspect current inputs and prices before paid calls.
Total authorized research budget: [amount]. Stop at that limit.
Preserve source URLs, timestamps, currencies, units and filing dates.
List gaps and conflicts. Do not place trades or give a price target.

The budget covers retrieval and any paid analysis you authorize. It is a planning limit you choose, not a quoted cost for this recipe.

2. Resolve the ticker, then collect the snapshot

The current catalog includes openwebninja/finance-search, which takes a query, and openwebninja/stock-quote, which takes a symbol. Ask the agent to inspect the returned identity before using that symbol for the quote. Add history or news only when it answers the research question.

The quote action has no historical as-of parameter. For a past date, select a history route with the required coverage instead of relabeling today's quote.

Keep retrieval time separate from the quote's own time. A freshly retrieved response can contain delayed or earlier-session data. Preserve a delay label if supplied; if it is absent, leave freshness unverified. Do not silently stamp the retrieval time onto an old observation.

Save the original response alongside the extracted fields. That makes it possible to check whether a later discrepancy came from the provider, a unit conversion or the agent's summary.

3. Join the company to its filings

For a US reporting company, Vaaya exposes edgar/entities to search by name, edgar/filings to retrieve history using a CIK, and edgar/document for a filing identified by CIK, accession and filename. Take those identifiers from the returned records rather than inventing an archive URL.

Select the filing and reporting period deliberately. A filing date is when information was submitted; the financial period describes the business activity it reports. An amendment can change the relevant record without changing the period being discussed.

The SEC's API documentation explains its submission and XBRL data. For structured financial facts, retain the taxonomy, concept, unit and start/end dates. If a requested concept is missing, read the statement instead of treating the missing value as zero.

4. Return a table someone can check

Use a worksheet like this. These are field requirements, not results from a stock analyzed for this article.

Field	What the agent must preserve
Security	Company, ticker, exchange and share class
Quote	Price, currency, source time and session or delay information
Financial fact	Value, unit, fiscal period and definition
Filing	Form, accession, filed date and original link
Open question	The conflicting or missing evidence and next source to check

Before comparing two years, confirm that both rows describe the same measure and duration. Keep a reported figure separate from a calculation the agent performs. Show the calculation inputs so another reader can reproduce it.

5. Stop with an evidence packet

Have the agent return the short brief, worksheet and source files together. Reject uncited numbers and summaries that turn a missing field into a confident conclusion. If an endpoint fails, preserve the completed research and ask whether another source is worth the remaining budget.

For a broader workflow, Vaaya's trading research guide provides additional starting points. End this run when the stated question has a traceable answer or a specific list of missing evidence.

Questions

Can an agent use this workflow to place a trade?

This tutorial only retrieves and organizes research. A quote, company brief or catalog connection does not authorize a trade.

Why do two sources show different revenue figures?

They may use different fiscal periods, currencies, units, filing versions or adjusted definitions. Preserve those fields and reconcile them against the filing before comparing.

Does a quote returned now have a current market timestamp?

Not necessarily. Keep the provider timestamp, market session and delay label where supplied. Record freshness as unknown when the response does not establish it.