Top Repos· Jev-Based· SDK· Last updated

typesafe-ai / typesafe-sdk-js

“The official TypeScript/JavaScript library for the TypeSafe API”

Jev-Based rank #18In SDK #4

TL;DR

typesafe-ai/typesafe-sdk-js 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: “The official TypeScript/JavaScript library for the TypeSafe API” 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, LICENSE, README.md, biome.json, docs, examples, jsr.json, package-lock.json, package.json, scripts, src, test, tsconfig.dist-test.json. Read those before you trust a one-line install.

How to use

  1. Install the vendor JS client (Node 20+).
npm install @typesafe-ai/sdk
  1. Call POST https://api.typesafe.ai/v1/systemone through the SDK — do not invent extra TypeSafe routes.
  2. Log the response model field so an alias move is visible.

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

{
  model: "jev-1.13.0",
  state: { source: "typesafe-ai/typesafe-sdk-js", 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/typesafe-sdk-js 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/typesafe-sdk-js 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.