
**The problem.** Angel investors, VC scouts, and accelerator reviewers screen 20–50 startups a month. Before the first meeting they have no tooling — just Google and gut. The only question that matters is "is this worth a call?", and nothing answers it fast. **What DealScope does.** Paste a company's URL. Autonomous agents read its public footprint — website, GitHub activity, public hiring boards — and return a structured deal screen: a verdict (Worth a call / Borderline / Pass), a risk matrix, bull and bear cases, and a confidence score. **Every claim links to the public source it came from**, so you can click and verify it yourself. The one model-opinion section (market) is labeled as such — we never fake a source. That's the difference from pasting a URL into ChatGPT: no hallucinations you can't check. **How it uses AMD — the cost engine.** Screening one company means reading 100+ pages, which is a lot of LLM calls. DealScope routes across two AMD-hosted models on Fireworks: a cheap model (gpt-oss-120b) does the high-volume extraction, and a premium model (deepseek-v4-pro) writes only the final verdict. A naive pipeline that uses the premium model for everything costs ~3.6× more. The cost-race is shown live and computed from real token counts × published Fireworks rates — the hackathon's token-efficiency thesis shipped as a product, on AMD Instinct silicon. **Built for real.** One FastAPI container serves the API and a streaming instrument-panel UI over Server-Sent Events. Runs can be recorded and replayed. 33 unit tests plus a golden-company integration harness. MIT-licensed and public on GitHub. A gallery of eight real company screens ships in the repo and replays instantly. **Who it's for.** ~300,000 US angels are untooled for the pre-meeting screen, plus micro-VCs, scouts, and accelerator reviewers. DealScope is the 30-second "worth a call?" — with receipts.
13 Jul 2026

Adds a demo route (/api/demo/402-flow) and an info endpoint to illustrate an HTTP 402 payment flow in-app. A first request (no X-Payment-Tx) returns a 402 JSON with payment.instructions, receiver, amount, and a demoTxHash; repeating the request with X-Payment-Tx: demo-payment-0x1234567890abcdef returns mock Aave yields data and paymentVerified: true. Includes a runnable helper script demo-402.sh that defaults to HTTPS, follows redirects, accepts an optional API_KEY env var (X-API-Key), and pretty-prints JSON when jq is available — use HOST and API_KEY to point at a deployed host. Intended for live demos and documentation to show the exact UX of requiring payment proof, how to present the 402 payload, and the transition to successful access. Note: ensure the backend API_KEY_SECRET matches the frontend VITE_API_KEY (or supply API_KEY when running the script).
24 Jan 2026