jevcache
jevcache (jevcache.
Overview
jevcache from hyperspaceai memoizes structured Jev answers keyed by model, schema, and state hash. The jev backend talks to TypeSafe with your local API key; decide, recall, replay, and serve commands expose hits, misses, and replays for debugging spend.
Problem: Agents replay identical decide questions on unchanged state, paying inference micro-dollars for deterministic answers they already bought.
Built for: Operators who want a local ledger for Jev-class decisions with CLI audit trails, not another hosted proxy holding their keys.
First indexed on Jev Directory: 2026-09-22
Creator and team
- Name
- hyperspaceai
- Handle
- @hyperspaceai
How Jev is used
- Role in the product flow
- Local cache and replay layer in front of TypeSafe Jev calls
- Primitives
- ChoiceScoreNoul
- State in
- Tuple of model id, JSON schema fingerprint, and canonical serialized state presented to decide.
- Decision out
- Cached structured answer on hit; on miss, forward to Jev, persist, then return. replay reproduces prior decisions for audits.
- CLI or serve endpoint receives decide with schema + state
- jevcache hashes inputs and checks the local ledger
- On miss, call TypeSafe Jev and store response with metadata
- recall and replay commands inspect history without re-spend
jevcache is infrastructure, not a new primitive. Whatever schema you pass (Choice among tools, Score for risk, Noul for allow) is what gets cached. The project is explicit that it is not reselling inference: your key stays on the machine running jevcache. That makes it attractive for agent loops that re-read the same repository snapshot or policy table every turn. Use serve when multiple workers should share one ledger; use replay when finance asks why the bot flipped a gate last Tuesday.
Features and stack
Features
- Memoize (model, schema, state) to Jev answers
- CLI decide, recall, replay, and serve
- Local TypeSafe key, not a proxy reseller
- Works with any primitive your schema defines
Stack
- TypeScript
- CLI
- local ledger store
- TypeSafe System One
Pricing: Cache hits avoid repeat Jev charges; misses bill normally through TypeSafe.
Links
FAQ
- Does jevcache host my API key in the cloud?
- No. README positions the tool as a local decision ledger with your TypeSafe credentials on the operator machine.
- Which primitives can I cache?
- Any structured decide schema you define: Choice, Score, or Noul shaped questions all serialize into the same cache key pattern.
Related learn guides
Original Jev guidance that pairs with this product pattern.
- Jev & TypeSafe
A primer for builders who need to know what Jev is, who it is for, and when TypeSafe docs should take over from this directory.
- System One model
The model family behind Jev: parallel typed questions, one forward pass, probabilities you can threshold.
Related products
Hand-picked neighbors with rich profiles or overlapping tags.