Bounded freshness pass · 24 Sep 2026

Two corrections, not a catalogue-wide refresh

A 24 September direct-source check found a newer displayed TypeSafe MCA date and tiered prices on an independent proxy. The builder decision stays conditional on account and data checks.

Scope: This pass checked selected fields in the existing source set. It did not run an authenticated Jev call, purchase, benchmark, broad product search, or full alternatives audit. Earlier source records remain dated 20 Sep for access, 22 Sep for alternatives, and 23 Sep for products unless a field below was rechecked.

Change-detection ledger

Field checked 24 Sep	Direct observation	Decision boundary
TypeSafe MCA	It displays “Last updated Sep 23, 2026”, versus Sep 19 recorded on 20 Sep. Current §§4.1–4.3 permit service/fee processing and telemetry and say Customer Data is not used to train model weights without prior consent. Current §8.2 includes credit expiry terms.	The exact textual or legal diff is unknown: no archived Sep 19 body was available. Credit expiry is a current clause, not a proven new clause. Review the current MCA, DPA, and chosen route before sensitive data.
Independent proxy price	Self-reported input rates: $0.42/M for $5/$10/$20 packs, $0.35/M for $50, and $0.25/M for $100; output free. The page describes an independent, non-TypeSafe-affiliated service.	The 20 Sep report listed only $0.42/M and a $5–$100 range. This is a record correction, not proof of a later price change. Purchase, account terms, retention, and live access remain unverified; these are not TypeSafe direct rates.
Waitlist wording	A Join Waitlist link was observed on 20 Sep. The fetched home text on 24 Sep did not show it; the console still redirected to login.	Missing text is not proof the waitlist ended. Key access, credits, quota, and eligibility remain unknown.

What did not change the decision

The checked model and API pages still displayed jev-1.13.0, the two aliases, $0.042/M direct input, free output, published limits, and POST https://api.typesafe.ai/v1/systemone. OpenRouter and Cloudflare retained their listed Jev routes; Cloudflare's numeric account price remained unavailable publicly. The Vercel page and the killmyidea host were inaccessible to this checker, not proven absent.

Lightweight repository indicators did not justify a new adoption claim: killmyidea remained at 9 commits, Jev Showcase at 4, and jev-usecases at 8; the tool-router demo remained explicitly mocked. Awesome Jev rose from 199 to 201 commits, but a directory count is neither a product audit nor adoption evidence. No full-file diff or new lead review was done.

Bounded findings remain: the 22 Sep six-source alternatives audit found no verified open-weight Jev model, and the 23 Sep checked leads found no verified production product. Neither is a universal negative, and neither audit was rerun on 24 Sep.

Next checks

Find the Sep 19 MCA body or a TypeSafe changelog before describing clause changes.
Test a real direct account for key, credits, quota, and actual billing; separately review any gateway or proxy account terms.
Keep production use and adoption unknown until a public operation or customer trace is directly verified.

Research run run:manual:60f0123d612489bea7f4a5253ad7209c; direct checks 24 Sep 2026. No analytics or authenticated account access was available. Return to the route comparison.