Read filing evidence with Gemini CLI

Select FY rows by periodEnd instead of assuming the array is latest first. Source statements may present comparative years in one filing. Their later publication does not prove those exact restated values were available at the earlier historical date.

Scroll sideways to compare all columns. Select a heading to sort.

No matching rows. Clear the filter to see all records.

NexusTrade sec_edgar read recorded October 10, 2026. The reporting period ended 2025-12-31; the filing date was 2026-02-06.

Revenue

$716.924B716,924,000,000 USD

Operating income

$79.975B79,975,000,000 USD

Operating margin

11.16%Calculated as operating income ÷ revenue.

Operating margin describes this reported period. Keep annual and quarterly values separate, select the matching period explicitly, and retain the source filing. The fundamentals array includes older observations and is not ordered latest first.

Create research/amzn-cash-flow.md as the evidence record. Keep issuer identity, metric, unit, fiscal period, publication date, URL and the exact source passage together. The worked historical release below is a verification exercise, not the company's latest report.

Read Amazon (AMZN)'s Q4 2024 release published February 6, 2025. Extract operating cash flow for the twelve months ended December 31, 2024 and December 31, 2023, with USD units and source links. Save research/amzn-cash-flow.md with the subtraction and growth calculation. Distinguish annual cash flow from quarterly earnings. Do not submit research_topic or other paid work before I approve it.

Amazon published its fourth-quarter 2024 results on February 6, 2025. Its cash-flow statement reports operating cash flow of $115,877 million for the twelve months ended December 31, 2024 and $84,946 million for 2023.

The difference is $30,931 million. 30,931 ÷ 84,946 × 100 is about 36.4%, consistent with the release's rounded 36% growth. This is operating cash flow, not free cash flow, and the annual period is not the quarter alone. It establishes a historical comparison, not an investment return.

Call sec_edgar twice with the separate argument objects below. list_filings returns filing references; fundamentals reads inline XBRL metrics. Inspect filing dates, fiscal periods and units before comparing them with the historical release. The five recent filings may not include that older release. Missing evidence is a gap to resolve from the primary source, not permission to fill in a number.

Keep these reads separate from ingest_filings, which persists source text. For AMZN, annual periods preserve the twelve-month comparison.

{
  "ticker": "AMZN",
  "action": "list_filings",
  "forms": [
    "10-K",
    "10-Q"
  ],
  "limit": 5
}

{
  "ticker": "AMZN",
  "action": "fundamentals",
  "periods": "annual"
}

Scroll sideways to compare all columns. Select a heading to sort.

No matching rows. Clear the filter to see all records.

research_topic is asynchronous. Poll get_research_status with the same job ID instead of launching another billed research run for the same question.

If the primary sources leave a specific question unresolved, show the exact message for research_topic first. The accepted response includes researchJobId and status; save them before ending the session. A completed inline response may already contain citations. Otherwise pass the saved researchJobId as research_job_id to get_research_status.

PROCESSING means poll the same job. COMPLETED returns the report content and citations. FAILED returns an error to investigate. A second research_topic call starts another billed run; a missing response is not permission to duplicate it. If no saved ID exists, inspect the original tool response before considering another submission.

If the server is missing, check whether you selected user or project scope. Use /mcp reload to rediscover tools after configuration changes. For expired tokens, repeat /mcp auth nexustrade. Shell gemini mcp list can show connection errors. After an interrupted terminal session, reopen the saved run ledger or /resume and continue with the recorded job or deployment ID.

Open research/amzn-cash-flow.md and check each material claim against its link. Keep the original reported value and label each calculation. Leave absent/restated evidence explicit. For a newer-period brief repeat the source checks with the actual latest publication dates instead of carrying these historical figures forward.

The finished artifact should contain the source table, reproducible arithmetic, a bounded interpretation and the next unresolved question. It is a research brief, not a saved strategy or order instruction.

The local brief records your sources and calculations. A research_topic submission can consume credits, so review its exact question and your plan before starting it. Reuse the accepted job ID when polling or recovering a session. Check each report claim against its cited source.

For live deployment, review the separate broker guide, exact trading account and permissions. Choose the broker guide that matches your trading account.

On October 10, 2026, we called sec_edgar with the two separate request objects below. The product returned a AMZN 10-K filed 2026-02-06, for the fiscal year ended 2025-12-31, and the FY2025 metric row shown here. We selected that row by fiscal year and period end, rather than assuming the first array entry was latest.

The amounts below are USD, while the linked issuer statement displays them in millions. Revenue and operating income answer different questions from operating cash flow. The compact fundamentals row does not supply operating cash flow; do not relabel freeCashFlow as that metric.

This receipt records a NexusTrade filing read on October 10, 2026. Optional historical exercises retain their own periods and units.

No matching rows. Clear the filter to see all records.

{
  "ticker": "AMZN",
  "action": "list_filings",
  "forms": [
    "10-K"
  ],
  "limit": 1
}

{
  "ticker": "AMZN",
  "action": "fundamentals",
  "periods": "annual"
}

Scope choice

This command uses user scope. Use project scope if the connection should belong only to this workspace.

With Gemini CLI installed, run the registration command below in your research workspace. Start gemini, enter /mcp auth nexustrade and finish NexusTrade browser sign-in. Use /mcp list to inspect the tools.

What you should see: The user-scoped server is available across projects. Google sign-in and NexusTrade account authorization remain separate.

gemini mcp add --transport http --scope user nexustrade https://nexustrade.io/api/mcp
gemini mcp list

Skip this step if you only want to inspect the public filing in the next step. Before reading or changing an owned portfolio, ask for a read-only list, inspect one returned ID with get_portfolio and compare its name, strategies and deployment type. An authenticated empty list is valid for a new account.

What you should see: For owned records, you have the intended account response or an authenticated empty response. Resolve an account mismatch before saving anything. Public filing inspection does not require an owned-portfolio read.

Identity boundary

A server list or public filing read does not verify access to your owned portfolios.

Use only NexusTrade read tools. Call fetch_portfolios, then get_portfolio with one returned portfolio ID. Report the ID, name, strategies and deployment type. If the authenticated list is empty, report that result. Do not create, edit, backtest, deploy or place orders.