Versions and timeline (models, SDKs, API, company)

TL;DR Everything ships in a two-week window around 2026-09-15, the launch. Current versions as of the wiki's snapshot date 2026-09-21: model jev-1.13.0, API v1 (OpenAPI info.version 0.2.0), Python typesafe-sdk 0.7.1, JavaScript @typesafe-ai/sdk 0.6.0, Claude Code plugin typesafe 0.5.7, system-one-adapter 0.2.0. Two date conflicts matter: the JS 0.5.7 changelog date disagrees with npm by a day, and jev-1.13.0 was already answering production calls on 2026-09-11, four days before the release date the OpenAPI document gives for jev-latest.

Snapshot date: 2026-09-21. Every "current" statement on this page is as of that date, when raw/MANIFEST.json was re-fetched and the PyPI/npm registries were re-checked (registry_checked: "2026-09-21"). The previous snapshot was 2026-09-17; rows carrying that date are the state at that earlier fetch. Dates are taken from the sources named in the last column; nothing here is inferred from file mtimes.

Master chronology

Model versions

TypeSafe publishes no model changelog. Only two versions are attested anywhere in the sources.

jev-1.0 through jev-1.11 are not mentioned in any source. Aliases: jev-latest and jev-preview both point at jev-1.13.0, and the docs warn that "jev-preview currently points to the same model as jev-latest. There is no preview build available right now." Aliases move silently on release, so the response's model field is the only record of which version answered (Models, aliases, pricing, rate limits, context).

API versions

The OpenAPI document captured on 2026-09-17 declares openapi: 3.1.0 and info.version: 0.2.0 — a document version, not an API version; the paths are /v1/systemone and /v1/models (OpenAPI component schemas). It was not among the sources that changed in the 2026-09-21 refresh, so the wire contract is unchanged. Full migration deltas: Migrating from /preview/evaluation to /v1/systemone.

Python SDK — typesafe-sdk

Repo re-captured 2026-09-21 at commit 0ffd094c72ed9445223060b24ffd7a56aa781fb4; pyproject.toml declares version = "0.7.1" and its dependencies are now httpx2>=2.0.0, pydantic>=2.12.0, pydantic-core>=2.41.1, tenacity>=9.0.0, typing-extensions>=4.13.0 — msgspec is gone. The previous capture (2026-09-17) was commit 420ef4ffb612d5a539a1e0f0fe883ff6770340af ("Release v0.6.0", 2026-09-15). Predecessor package typesafe-client (0.1.x and 1.0.x, undated) sends document and no longer works. typesafe-ai 0.1.0 on PyPI is a redirect shim; the unrelated typesafe 0.9.1 is not TypeSafe AI's (Python SDK changelog).

JavaScript SDK — @typesafe-ai/sdk

Repo pinned at commit 66880ccded6cb642dc1809620c2b108c33730214 ("Release v0.6.0", 2026-09-15); package.json, jsr.json and src/version.ts all read 0.6.0 (JavaScript SDK changelog). The 2026-09-21 refresh found no change: the checkout is at the same commit and the registry check recorded sdk_js: "0.6.0". The two SDKs have diverged — Python is at 0.7.1 with a pydantic core, JavaScript is still at 0.6.0.

Other packages

Two adapter releases landed on the same day, 2026-09-18: 0.1.5 pinned the adapter below typesafe-sdk 0.7.0, and 0.2.0 moved it across. If you are on typesafe-sdk 0.6.x, stay on adapter 0.1.5; on 0.7.x you need 0.2.0 (system-one-adapter: LLM-backed drop-in for TypeSafeClient).

Legal documents

Repository commits captured (from raw/MANIFEST.json, fetched 2026-09-21)

The manifest records no commit date for the two re-captured repos, only the capture date, so the 0.7.1 and 0.2.0 dates above come from the changelogs rather than from git. The JS checkout contains a single commit, so per-commit history before 0.6.0 is not available locally.

What changed between the two snapshots (2026-09-17 → 2026-09-21)

raw/LAST_REFRESH.md records 54 changed sources and 3 new ones. Most of the churn is presentational (mermaid actions={true}, removed diagram styling, whitespace). The substantive deltas:

Where the dates conflict

1. JavaScript SDK 0.5.7: 2026-09-11 vs 2026-09-12. The upstream changelog dates it 2026-09-11; the npm registry records the publish on 2026-09-12. Read the first as the release-tag date and the second as the registry timestamp (JavaScript SDK changelog).
2. jev-1.13.0 predates its own release date. It answered all 15 production calls in the consistency cookbooks on 2026-09-11, while the OpenAPI example gives jev-latest a release_date of 2026-09-15, the public launch day. Either the alias's release date refers to general availability rather than the model build, or the model was serving early-access traffic before launch. No source resolves this (inferred framing).
3. Latency and multiplier claims disagree across TypeSafe's own channels. The Business Wire release says "less than 100 milliseconds" and "up to 100 times faster and less expensive"; the docs and blog say 70–500 ms end to end; the homepage says 193.6x faster / 444.6x cheaper; the blog's comparison table says "40x-200x faster" for System One-shaped queries. The multipliers measure different things — the demo shape versus the four workflow evals — but the press-release figures match neither (Press and third-party coverage, Workflow evals: how TypeSafe measures Jev).
4. Cookbook price comments carry two different dates for the same constant. PRICE = (0.042, 0.00) is annotated "TypeSafe jev-1.12 as of 2026-08" in some cookbooks and "as of 2026-09" in others, and the consistency cookbooks label the same figure "Historical TypeSafe rate, as of 2026-08" while pinning jev-latest. The comment dates the price, not the run (Models, aliases, pricing, rate limits, context).
5. The Privacy Policy is stale relative to the product. Dated 2025-11-19, it predates the MCA, the DPA's current version, and the launched product surface it describes (Legal: MCA, DPA, privacy, data retention).
6. Version numbering has unexplained jumps. Both SDKs' first public release is 0.5.7 rather than 0.1.0, and system-one-adapter starts at 0.1.3; no source explains either. As of 2026-09-21 the plugin sits at 0.5.7, the JS SDK at 0.6.0, the Python SDK at 0.7.1 and the adapter at 0.2.0 — the four version lines are independent and no source claims otherwise.
7. Undatable items. The preview API era, the "first v1 releases" that still accepted document, the typesafe-client releases (0.1.x, 1.0.x), and typesafe-sdk 0.0.1a0 carry no date in any source. Do not infer one. The new introduction/coding-agents docs page is also undated upstream; all that can be said is that it was absent from the 2026-09-17 sitemap and present in the 2026-09-21 one.
8. The waitlist has disappeared from typesafe.ai but survives in the launch material. Every typesafe.ai page captured on 2026-09-21 shows "Docs / Sign in / Contact sales" where the 2026-09-17 captures showed "Join Waitlist," and no page fetched on 2026-09-21 — site, docs, or console — contains the word "waitlist." The launch blog ("bringing developers off the waitlist as quickly as we can") and the 2026-09-15 Business Wire release ("Early access to its first frontier model, Jev, is waitlisted at typesafe.ai") are unchanged and still say otherwise, as do the third-party guides written on 2026-09-16/17. No source states what replaced the waitlist, so treat the gate as unstated as of 2026-09-21 rather than open (console.typesafe.ai (console + playground)).

Related

• Migrating from /preview/evaluation to /v1/systemone — what changed between the two API generations
• Python SDK changelog / JavaScript SDK changelog — the per-release detail
• Models, aliases, pricing, rate limits, context — aliases, and why to pin a version
• Jev (model) — the model as an entity
• TypeSafe AI (company) — company facts and funding
• typesafe-ai GitHub organisation and repos — the repos and their push dates
• Blog: AI: too good to be true, too bad to be useful (2026-06-19) — 2026-06-19, the oldest captured post
• FAQ for agents and developers / Glossary — the rest of this synthesis set

Sources

• wiki pages listed in the frontmatter (all under wiki/)
• raw/MANIFEST.json — fetched: 2026-09-21, registry_checked: 2026-09-21, sdk_python: "0.7.1", sdk_js: "0.6.0", four pinned git commits
• raw/LAST_REFRESH.md — "Refresh report 2026-09-21": 54 changed sources, 3 new, 0 fetch failures
• raw/github/typesafe-sdk-python/docs/changelog.md — v0.7.0 (2026-09-18) and v0.7.1 (2026-09-21) entries; raw/github/typesafe-sdk-python/pyproject.toml — version = "0.7.1", pydantic dependencies
• raw/github/system-one-adapter-python/docs/changelog.md — v0.1.5 and v0.2.0, both 2026-09-18; raw/github/system-one-adapter-python/pyproject.toml — version = "0.2.0", typesafe-sdk>=0.7.0
• raw/sitemap.xml, raw/llms.txt — introduction/coding-agents added; the sdk/python/api/clients/* restructure
• raw/site/openapi.json (https://docs.typesafe.ai/openapi.json) — info.version 0.2.0; jev-latest example release_date: "2026-09-15"
• raw/site/typesafe-ai-legal_mca.txt, raw/site/typesafe-ai-legal_data-processing.txt, raw/site/typesafe-ai-legal_privacy-policy.txt — "last updated" dates
• raw/docs/cookbooks__skill_suggestion.md, __autoresearch_feature_discovery.md, __entity_alignment.md, __classification_using_confidence.md, __llm_guardrails.md, __citation_check.md — dated jev-1.12 runs
• raw/docs/cookbooks__consistency_choice_cookbook.md, __consistency_noul_cookbook.md — "sampled on 2026-09-11", "TypeSafe returned models (calls): {'jev-1.13.0': 15}"
• raw/site/typesafe-ai-.txt (https://typesafe.ai/), raw/site/team.txt — the 2026-09-21 captures, whose navigation reads "Docs / Sign in / Contact sales". The superseded 2026-09-17 capture is kept at raw/site/typesafe-ai-home.txt, where the same navigation reads "Join Waitlist" and the page clock reads "Thursday, Sep 17, 2026"