Community project / Client libraries and integrations

Jev-Switch

Rust gateway with a React console and Windows Tauri app that serves a Jev-shaped /v1/systemone endpoint and routes each request through an editable graph of upstream routes with failover; v0.1.0 adapters cover only Vercel AI Gateway and Laya, not TypeSafe's own API, request state goes to the selected upstream, and the README is in Chinese.

Open the original resource ↗ See it in the full directory Start a reading list → Browse all Client libraries and integrations

Download share card ↓

This is an independent community listing. Check the source, license, data handling, and evaluation caveats before relying on a project. Inclusion is not an endorsement or security review.

Found an outdated or inaccurate detail? Report a correction →

Explore more in Client libraries and integrations

• 

  Jevelry

  Early-stage TypeScript CLI, library, and coding-agent skill for reusable Jev question templates: it maps typed answers to act, mark, or fall back, and keeps a local decision/outcome log for review. Question state goes to TypeSafe; the log keeps a state hash by default but can opt into full state, and configured run commands may execute locally without per-action confirmation when confidence is high.

  Read listing →
• 

  jevframe

  Early Python library adding async Jev Noul, Choice, Score, and multi-question evaluation to pandas and eager Polars, with full Choice and Score probability distributions, bounded row concurrency, and opt-in memory caching; each uncached row sends selected context to TypeSafe, and LazyFrame expressions are outside v0.

  Read listing →
• 

  jevql

  psql-shaped CLI and Go/TypeScript/Python SDKs that let you write WHERE jev(alias, 'condition'), jev_prob, jev_choice, and jev_score against a vanilla Postgres with no extension: it runs the plain SQL on the server, judges the surviving rows with Jev in batches (cached in local SQLite), and applies filter, sort, and group in the client; every row that survives the SQL filters is sent to TypeSafe and judged, so put cheap predicates in SQL first.

  Read listing →