Top Repos· Jev-Based· SDK· Last updated

typesafe-ai / system-one-adapter-python

“Drop-in TypeSafeClient replacement backed by LLM APIs”

Jev-Based rank #15In SDK #2

TL;DR

typesafe-ai/system-one-adapter-python is vendor GitHub — treat it as a TypeSafe source, not a jev.pro artifact. Canonical request facts stay on docs.typesafe.ai.

The author describes it as: “Drop-in TypeSafeClient replacement backed by LLM APIs” That is their claim, not a bench this site ran.

Who it’s for

What’s inside

Top-level entries on GitHub at generation time: .github, .gitignore, .python-version, LICENSE, README.md, docs, pyproject.toml, pyrefly.toml, src, tests, uv.lock. Read those before you trust a one-line install.

How to use

  1. Clone and follow the author’s Python toolchain. Do not invent a package name.
git clone https://github.com/typesafe-ai/system-one-adapter-python.git
cd system-one-adapter-python
  1. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
  2. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "typesafe-ai/system-one-adapter-python", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

First pinned call

Call typesafe-ai/system-one-adapter-python with model jev-1.13.0, a two-sentence support ticket as state, and questions: refund_asked (noul), department (choice: billing|tech|other). Print choice, noul, confidence, and model.

Schema-safe ≠ correct

On a case typesafe-ai/system-one-adapter-python gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Is this the Jev model?

No repository is the model. Jev is the hosted System One instance. This repo is vendor code around the API.

Can I get a key here?

No. Keys come from TypeSafe’s console or a documented gateway.

Sources

Public repository metadata and TypeSafe documentation. No private claims.