resources / ecosystem directory
Jev resources: official docs, SDKs, and tools
A structured ecosystem directory separating authoritative primary documentation from community SDKs, playgrounds, MCP servers, and research.
Quick Guide: Navigating the Jev Resource Ecosystem
The Jev ecosystem is evolving rapidly across official specifications, community SDKs, interactive playgrounds, MCP servers, and academic research. This directory maintains a strict division between primary authoritative sources and third-party projects. We recommend anchoring on official TypeSafe docs for baseline API contracts while leveraging community tooling to accelerate execution.
Starter Toolkit
First-Day Recommended Starter Stack
New to Jev? We recommend starting with this verified three-part toolkit:
Official Primary Docs (TypeSafe AI)
Verify authentic API endpoints, model identifiers (`jev-1`), and token billing parameters directly from the source.
Jev 101 Interactive Playground
Test real-world state inputs and choice probabilities in your browser with zero local environment setup.
Jev MCP Extension Server
Connect Jev decisions into Model Context Protocol hosts like Cursor and Claude Desktop to orchestrate typed logic.
Official
TypeSafe AI docs
Primary documentation for Jev and System One Models.
Primary source
Official
TypeSafe Jev announcement
The original introduction to Jev and the decision-model category.
Primary source
SDKs
Jev TypeScript SDK
A starting point for typed decisions in Node and web apps.
Independent community project
Tools
Jev Playground
A community playground and pricing reference.
Independent community project
MCP
jev-mcp
A community MCP server for Jev decision tools.
Independent community project
Research
ModelSystem.One
A broader view of the emerging decision-model category.
Independent community project
Community
Jev 101 directory
A neighboring Jev guide and directory with broader community coverage.
Independent community project
Verification & Directory Standards
All catalog entries are vetted against these transparency criteria:
Strict Provenance Labeling
Official primary materials are explicitly segregated from independent open-source contributions.
Open Source Transparency
Third-party tools and SDKs must be backed by public repositories licensed under recognized terms (MIT/Apache-2.0).
Protocol Parity Verification
We regularly audit ecosystem libraries against the latest Jev inference specs, pruning broken or abandoned packages.
Zero Credential Leakage
We reject tools that proxy API keys through untrusted intermediaries or include telemetry exfiltration.
Frequently Asked Questions (FAQ)
Does Jev provide an official native SDK for all languages?
TypeSafe maintains the official HTTP REST API specification. Community packages exist on npm and PyPI. Because the Jev contract is concise, many production teams write a lightweight 20-line fetch wrapper rather than adding external dependencies.
What is the Jev Model Context Protocol (MCP) server?
MCP is an open standard connecting AI models to external tools and data sources. The Jev MCP server exposes typed decisions as tools, allowing coding agents in Cursor or desktop assistants to execute classification steps seamlessly.
What security precautions should I take with community tools?
Never enter production provider API keys into third-party closed-source web forms. When running open-source CLI tools or SDKs, inspect the codebase to confirm network calls route directly to verified provider endpoints.
How do I submit an open-source Jev project to this directory?
Submit a pull request or issue to the Jev 101 repository. Include a link to the open repository, license terms, a concise feature overview, and a verified minimal usage example.
What takes precedence when community guides contradict official docs?
Always defer to the official TypeSafe AI documentation (docs.typesafe.ai). Community articles can fall out of sync after upstream model or parameter updates.