Inspiration
Every day we're bombarded with claims, AI-generated content, and information that may or may not be true. Fact-checking is slow, manual, and unreliable. We wanted to build something that could repair broken information signals automatically — using the live web, multiple AI models, and real evidence.
The domain signal.repair perfectly captured the idea: information is a signal, and when it's broken, noisy, or wrong, we repair it.
What it does
Signal.repair is a multi-agent AI system that verifies any claim, topic, URL, or AI-generated text in under 3 seconds.
Paste anything. Get the truth.
- Scout Agent searches 50+ live sources via Nimble's real-time web intelligence APIs, with Tavily as fallback
- Critic Agent scores credibility, assigns stances, finds contradictions between sources
- Consensus Engine runs 3 LLMs in parallel — majority wins, all disagree = DISPUTED automatically
- Signal Score — animated EKG oscilloscope showing 0-100 truth score
- URL Analyzer — paste any article URL, get per-claim credibility scores
- Claim Battle — two claims enter, evidence decides the winner
- Trend Radar — real-time analysis of the world's most disputed topics
- DNA of a Lie — visual timeline showing how misinformation originates and spreads
- Signal History — all repairs stored in Tower's lakehouse pipeline with analytics
- Browser Extension — right-click any text on any webpage to repair it instantly
How we built it
Backend: Python + FastAPI with Server-Sent Events for real-time streaming. Nimble for live web intelligence. Tavily as fallback search. Groq for ultra-fast LLM inference across 3 models simultaneously. Tower for serverless pipeline orchestration and lakehouse storage.
Frontend: React + TypeScript with Framer Motion animations. Custom Canvas API for the EKG oscilloscope meter and animated source credibility network graph. Full dark/light mode.
Browser Extension: Chrome Manifest V3 with context menu integration — select any text on any webpage and repair it instantly.
Architecture:
User Input → Scout (Nimble + Tavily) → Critic → Consensus Engine (3 LLMs) → Signal Score → Tower Lakehouse
Deployed:
- Frontend: Vercel (https://signal-repair.vercel.app)
- Backend: Render (https://signal-repair.onrender.com)
- Pipeline: Tower Cloud (v5, Run #10 successful)
Challenges
- Building real-time SSE streaming with FastAPI's async generators
- Getting 3 models to return consistent JSON for consensus voting
- Building a force-directed graph on Canvas without D3
- Tower deployment configuration and Towerfile format
- Nimble API authentication with hackathon whitelisting
What we learned
- Ensemble LLM approaches produce significantly more reliable verdicts than single models
- SSE is dramatically better than polling for real-time AI pipelines
- Tower's serverless compute is genuinely powerful for AI pipeline scheduling
- Nimble's real-time web intelligence provides significantly richer data than standard search APIs
What's next
- Email alerts when Signal Watch detects topic changes
- Enterprise API for newsrooms and research firms
- Multilingual support — repair signals in any language
- Mobile app
Built With
- canvas
- fastapi
- framer-motion
- gemma-2
- groq
- llama-3.3
- python
- react
- server-sent-events
- tavily
- tower
- typescript
Log in or sign up for Devpost to join the conversation.