What problem does it solve? Integrating with Archimedes' strategy generation pipeline requires knowing the exact /api/generate/* endpoint contract, the SSE stream's event shape, the real auth requirements (account session, not API keys or wallets), and how to interpret DSR/PBO/out-of-sample verdict fields without over-claiming what the numbers mean. ## Core Features & Use Cases - Endpoint reference: Documents POST /api/generate/start, GET /api/generate/stream/{job_id}, job cancel/list/candidates endpoints with file:line citations to the backend source. - SSE client guidance: Explains heartbeats, Last-Event-ID resume, the 300s stream timeout, terminal events, and the 14 event names on the wire so you can write a correct streaming client. - Auth and quota truth: Details Better Auth session login, the 409/402/202 payment error ladder, 5/minute rate limiting, and stacked daily per-user and per-IP quotas. - Honest verdict reading: Covers why n_candidates is not the DSR num_trials, why curated strategies are graded at num_trials=1, and why status "live" is not a rigor claim. - Use Case: An external agent calls POST /api/generate/start with a plain-English brief, streams the SSE verdict, and reports the strategy's DSR and PBO to its user with correct caveats. ## Quick Start Ask the agent to start a strategy generation job via POST /api/generate/start with a brief, then stream the verdict from the SSE endpoint and explain the DSR and PBO results.