This project provides a "Stockbroker Human in the Loop" agent, enabling users to interact with a stockbroker via a chat interface. It targets developers and power users looking to leverage AI for financial data analysis and decision support. The solution offers both a public API and a web-based chat interface for immediate use or integration.

How It Works

The project employs a monorepo architecture, separating the frontend and backend concerns. The frontend is a Next.js application facilitating user interaction through a chat interface. The core functionality is powered by a LangGraph agent, defining the stockbroker's decision-making process and data flow.

Quick Start & Requirements

• Installation: Run yarn install from the monorepo root to install all frontend and backend dependencies.
• Prerequisites: Requires API keys for Financial Datasets AI (https://financialdatasets.ai/), Tavily (https://tavily.com/), OpenAI (https://platform.openai.com/signup), and LangSmith (LANGCHAIN_API_KEY).
• Environment Variables: Configure .env files in ./backend and ./frontend directories with the respective API keys and URLs. Key variables include FINANCIAL_DATASETS_API_KEY, TAVILY_API_KEY, OPENAI_API_KEY, LANGGRAPH_API_URL (defaults to http://localhost:51497 for local dev, production URL provided: https://assistant-ui-stockbroker.vercel.app/api), and NEXT_PUBLIC_LANGGRAPH_ASSISTANT_ID=stockbroker.
• Deployment: Publicly accessible API at https://assistant-ui-stockbroker.vercel.app/api and a web chat interface at https://assistant-ui-stockbroker.vercel.app/.

Highlighted Details

• Features a LangGraph agent configured via ./backend/langgraph.json.
• Provides both a REST API and a user-friendly web chat interface.
• Monorepo structure simplifies management of frontend and backend components.

Maintenance & Community

No specific details regarding maintainers, community channels (like Discord/Slack), or roadmap were found in the provided README.

Licensing & Compatibility

The README does not specify a software license. Users should verify licensing terms before use, especially for commercial applications.

Limitations & Caveats

The project's functionality is heavily dependent on multiple third-party API services, requiring users to obtain and manage their own API keys. The README lacks explicit licensing information, posing a potential adoption blocker. The project description is listed as "None".