Explore the portfolio

Open to AI/ML and software engineering internships.

Back to portfolio

MarketMind

A market-research interface combining retrieval, market data, and portfolio-oriented questions.

Project archive Source

Historical project; AI-assisted development. Individual and team contribution has not been independently verified.

The idea

The problem

Market questions often need several kinds of context. Combine explicit data tools, portfolio arithmetic, and a streamed answer in one research interface.

The implementation

What I built

The implementation connects tool-driven market research with streamed answers and parsed portfolio context. The source scope is clearer than a general chatbot description, without implying profitable investment decisions.

  • Python
  • FastAPI
  • React

Features

  • Route research questions through market-data, news, technical-analysis, and portfolio tools.
  • Normalize CAMS-style CSV holdings into invested value, current value, and gain summaries.
  • Stream tool activity and responses to a React interface with stock-chart and portfolio views.

Architecture

  • React chat state and an SSE client connect to FastAPI streaming and portfolio-upload routes.
  • Python tool dispatch separates quote/news retrieval, indicators, and statement parsing; portfolio summaries become model context.

Engineering decisions

  • Keep portfolio arithmetic and data retrieval in explicit tools rather than relying entirely on generated prose.

Validation and measured results

  • Source reviewed on 15 October 2026. The application and its external integrations were not executed in this review.
  • Reviewed tool dispatch, CAMS column normalization, safe numeric parsing, and technical-indicator fallback code. No quote freshness, answer accuracy, or investment-return evaluation was run.

Limits and unfinished work

  • External market/news availability and statement formats can change behavior. No financial-advice reliability or return is established.
  • Older source can contain superseded descriptions. Numerical impact, adoption, awards, and deployment claims are not carried into this entry.

Evidence and sources

  • Reviewed source and implementation

    Public README and selected implementation files; source inspection only, without a reproduced runtime or benchmark. Inspected files: backend/agents/orchestrator.py, backend/agents/portfolio.py, backend/agents/technical.py.

Explore the project archive

Find your way

12 results found.

Use Tab or arrow keys to explore. Enter opens a result. Escape closes search.

Portfolio assistant

Answers from published portfolio records.

A closer look

Find the work behind the skills.

Ask about engineering decisions, validation, experience, or project limitations. Each answer links back to its sources.

AI can make mistakes. Check the linked records. Your question is sent to Google Gemini.