Oracle3
Open-source trading engine and MCP server for prediction markets. Fee-aware no-arbitrage trading across related contracts, live on Kalshi, Polymarket and Solana or on paper.
Track and analyze congressional stock trades with ML-powered predictions, pattern detection, and backtesting tools. Free, no signup required.
FinancePython · TypeScriptGitHub @ElliottSaxOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
AI-Powered Analysis of Congressional Stock Trading Activity
QuantEngines is a comprehensive, production-ready platform for analyzing congressional stock trading activity. It combines automated data collection, advanced analytics (ML predictions, options analysis, sentiment), and premium features (real-time alerts, portfolio tracking) with a professional web interface.Read the full README ↗AI-Powered Analysis of Congressional Stock Trading Activity
QuantEngines is a comprehensive, production-ready platform for analyzing congressional stock trading activity. It combines automated data collection, advanced analytics (ML predictions, options analysis, sentiment), and premium features (real-time alerts, portfolio tracking) with a professional web interface.
# 1. Clone the repository
git clone https://github.com/yourusername/quant.git
cd quant
# 2. Setup Backend
cd quant/backend
cp .env.example .env
# Edit .env with your settings (minimal: DATABASE_URL, SECRET_KEY, REDIS_URL)
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
pip install -r requirements.txt
# Run migrations
alembic upgrade head
# Start backend
uvicorn app.main:app --reload
# Backend now running at http://localhost:8000
# 3. Setup Frontend (in a new terminal)
cd quant/frontend
cp .env.local.example .env.local
# Edit: NEXT_PUBLIC_API_URL=http://localhost:8000
npm install
npm run dev
# Frontend now running at http://localhost:3000
# 4. Setup Data Pipeline (optional)
# Start Redis
redis-server &
# Start Celery worker
celery -A app.tasks.scraping_tasks worker -l info &
# Start Celery beat (scheduler)
celery -A app.tasks.scraping_tasks beat -l info &
That's it! Visit http://localhost:3000 to see the platform.
Backend:
Frontend:
Data Collection:
ML/Analytics:
Infrastructure:
┌─────────────────┐ ┌──────────────────┐
│ Next.js UI │ ←──→ │ FastAPI API │
│ (Port 3000) │ │ (Port 8000) │
└─────────────────┘ └──────────────────┘
↓
┌────────────┴─────────────┐
↓ ↓
┌──────────────┐ ┌──────────────┐
│ PostgreSQL │ │ Redis │
│ Database │ │ Cache/Queue │
└──────────────┘ └──────────────┘
↓
┌─────────────────┐
│ Celery Worker │
│ (Scrapers) │
└─────────────────┘
↓
┌─────────────┴──────────────┐
↓ ↓
┌─────────────────┐ ┌─────────────────┐
│ Senate Website │ │ House Website │
│ (efdsearch...) │ │ (disclosures...)│
└─────────────────┘ └─────────────────┘
cd quant/backend
# Create virtual environment
python -m venv venv
source venv/bin/activate # Windows: venv\Scripts\activate
# Install dependencies
pip install -r requirements.txt
# For production
pip install -r requirements.production.txt
# Configure environment
cp .env.example .env
# Edit .env with your configuration
# Run database migrations
alembic upgrade head
# (Optional) Seed database with test data
python app/scripts/seed_database.py
cd quant/frontend
# Install dependencies
npm install
# Configure environment
cp .env.local.example .env.local
# Edit .env.local
# Run development server
npm run dev
# Build for production
npm run build
npm start
See .env.example for complete configuration options. Minimum required:
Backend (quant/backend/.env):
# Core
PROJECT_NAME=QuantEngines
VERSION=1.0.0
ENVIRONMENT=development
SECRET_KEY=your-secret-key-min-32-chars
JWT_SECRET_KEY=your-jwt-key-min-32-chars
# Database
DATABASE_URL=postgresql+asyncpg://user:pass@localhost:5432/quant
# Redis
REDIS_URL=redis://localhost:6379/0
Frontend (quant/frontend/.env.local):
NEXT_PUBLIC_API_URL=http://localhost:8000
# Backend API
cd quant/backend
uvicorn app.main:app --reload --host 0.0.0.0 --port 8000
# Frontend
cd quant/frontend
npm run dev
# Redis (required for caching)
redis-server
# Celery Worker (for data scraping)
celery -A app.tasks.scraping_tasks worker -l info
# Celery Beat (scheduler)
celery -A app.tasks.scraping_tasks beat -l info
# Create new migration
alembic revision --autogenerate -m "description"
# Apply migrations
alembic upgrade head
# Rollback one migration
alembic downgrade -1
# View migration history
alembic history
cd quant/backend
# All tests with coverage
./run_comprehensive_tests.sh
# Specific test categories
pytest tests/test_api/ -v
pytest tests/test_integration/ -v
pytest tests/test_security/ -v
# Load tests
locust -f tests/performance/locustfile.py --host=http://localhost:8000
cd quant/backend
# Interactive deployment wizard
./scripts/quick_deploy.sh
# Or automated deployment
./scripts/deploy.sh production
# Build and run
docker-compose -f docker-compose.production.yml up -d
# View logs
docker-compose logs -f
# Stop
docker-compose down
See DEPLOYMENT_GUIDE.md for comprehensive deployment instructions.
Once the backend is running, visit:
Authentication:
POST /api/v1/auth/register - Register new userPOST /api/v1/auth/login - Login userPOST /api/v1/auth/refresh - Refresh tokenPoliticians:
GET /api/v1/politicians - List politiciansGET /api/v1/politicians/{id} - Get politician detailsGET /api/v1/politicians/{id}/trades - Get politician tradesTrades:
GET /api/v1/trades - List tradesGET /api/v1/trades/{id} - Get trade detailsAnalytics:
GET /api/v1/analytics/predictions - ML predictionsGET /api/v1/analytics/discoveries - Pattern discoveriesPOST /api/v1/analytics/options/gamma-exposure - Options GEX analysisGET /api/v1/analytics/sentiment/politician/{id} - Sentiment analysisPremium Features:
POST /api/v1/alerts - Create alertGET /api/v1/portfolios - List portfoliosGET /api/v1/subscriptions/current - Current subscriptionSee ADVANCED_ANALYTICS_API_REFERENCE.md for complete API documentation.
# Run all tests
./run_comprehensive_tests.sh
# View coverage report
open htmlcov/index.html
# Run load tests (requires running server)
locust -f tests/performance/locustfile.py --users 100 --spawn-rate 10
See TESTING_QUICK_REFERENCE.md for detailed testing guide.
Comprehensive documentation available in the repository:
Getting Started:
README.md - This fileQUICK_START_NEW_FEATURES.md - Feature overviewSESSION_2_FINAL_STATUS.md - Current status and next stepsFeature Guides:
DATA_PIPELINE_GUIDE.md - Data collection setupPREMIUM_FEATURES_DOCUMENTATION.md - Premium featuresADVANCED_ANALYTICS_API_REFERENCE.md - Analytics APIDeployment:
DEPLOYMENT_GUIDE.md - Complete deployment guidePRODUCTION_CHECKLIST.md - Pre-deployment checklistQUICK_START_DEPLOYMENT.md - Quick deploymentTesting:
TESTING_QUICK_REFERENCE.md - Test commandsTEST_SUITE_SUMMARY.md - Test suite overviewWe welcome contributions! Please see our contributing guidelines:
git checkout -b feature/amazing-feature)git commit -m 'Add amazing feature')git push origin feature/amazing-feature)Please report security vulnerabilities to [email protected]. Do not open public issues for security concerns.
This project is licensed under the MIT License - see the LICENSE file for details.
Current Version: 1.0.0 Status: ✅ Production Ready Last Updated: February 3, 2026
Built with ❤️ using AI-assisted development
Value: $65,000+ of development completed in 2 hours through parallel AI agent execution.