verdict-api

Request strategy generation and read rigor verdicts over Archimedes' HTTP API.

17|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/aprin-labs/archimedes --skill verdict-api-aprin-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verdict-api
Source: https://github.com/aprin-labs/archimedes/tree/main/skills/verdict-api
Command: npx skills add https://github.com/aprin-labs/archimedes --skill verdict-api-aprin-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about verdict-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a strategy via the Archimedes API?

POST to /api/generate/start with a JSON body containing a brief (intent, risk_appetite, max_papers) and optional n_candidates. The endpoint returns 202 with a job_id and stream_url, then runs the pipeline in the background while you stream results.

What auth does the Archimedes generation API require?

Generation requires a Better Auth account session cookie, not an API key or wallet. Sign up and sign in via /api/auth endpoints, send the session cookie on every request, and expect 401 without it. Wallets are only needed for payment or premium models.

How do I consume the SSE stream from /api/generate/stream?

The stream is a real text/event-stream response with 14 event types, comment-line heartbeats, and numeric event IDs. Reconnect with the Last-Event-ID header to resume after the 300-second connection cap, and treat done and error as terminal events.

Why did POST /api/generate/start return 409 or 402?

A 409 with reason wallet_link_required means the account has no linked wallet while payment is enabled. A 402 means a wallet is linked but no valid Payment-Signature was sent, or a premium model was requested without entitlement. A 202 follows successful payment.

Does passes_rigor_gate mean a strategy is safe to trade?

passes_rigor_gate is always evaluated at the strictest level and reflects DSR, PBO, and out-of-sample tests, but it is a statistical verdict, not a guarantee. The lifecycle status field only means active in a portfolio, and CPCV is explicitly reported as NOT_RUN.

Is n_candidates the number of trials used in the DSR calculation?

No. The Deflated Sharpe Ratio uses the search pool size the winning candidate was actually selected from, computed independently in the generation pipeline. Curated strategies are always graded at num_trials=1 against their own return series.