JevTools

A toolkit, knowledge base, web dashboard and reference implementation for building AI applications with Jev via OpenRouter Alpha Decisions and the TypeSafe Direct API. It bundles a dashboard, a Python CLI and library, a local SQLite request log, and an Obsidian-compatible vault of documentation.

GET /api/status reports engine status, provider, masked API key and benchmark counts. POST endpoints cover /api/analyze-review, /api/classify-topic, /api/custom-decision and /api/config, while /api/history is paginated with search and filtering, and /api/history/stats aggregates counts, success rates, latency averages and database size.

Demo 1 analyses customer reviews with a speculative fan-out of 6 questions, weighted composite scoring and action escalation. Demo 2 does multi-dimensional topic classification with property detection and confidence-gated routing. Flags include --review, --topic, --product, --json, --provider, --mock, --history and --clear-history.

In a zero-dependency local SQLite database, jevtools.db, which is strictly gitignored and used for personal device storage. It captures all outgoing requests, incoming responses, decision metrics, latency and status without third-party dependencies, and POST /api/history/clear plus DELETE /api/history purge and VACUUM it.

OpenRouter Alpha Decisions and the TypeSafe Direct API, with multi-provider auto-detection via --provider {openrouter,typesafe}. POST /api/config can dynamically update session keys, execution mode or provider, and GET /api/status reports the provider and a masked key.

There is offline mock testing with --mock for pipeline checks. Real analysis needs a provider key, since the dashboard's status endpoint reports a masked API key and /api/config can update session keys, execution mode or provider. The README does not describe the mock results as real judgments.

An Obsidian-compatible knowledge vault documenting Jev architecture, core concepts, design rules, SDKs and 18 cookbooks. It is reading material rather than code. The captured README describes vault/ and begins describing skills/ but the text is cut off there.