shipwithjev

Blog / Builds & people / FIG. 150

Every Jev Community Resource in One Page

Every Jev resource worth bookmarking: official docs, the TypeSafe Discord, community lists, SDKs, and where to go for each question.

Jev resources multiplied faster than anyone could bookmark them. Jev, the decision model from TypeSafe AI, launched in September 2026, and the ecosystem now has official docs, a Discord, several community lists, clients in half a dozen languages, and directories of directories. This page is the jev links hub: one place to start, sorted by the question you're actually asking. Terms get defined on the glossary; this page is for places.

Official sources

  • docs.typesafe.ai: the ruling source for API behavior, auth, limits, and the official SDKs (per its own index, Python and JavaScript). When anything below disagrees with it, it wins.
  • typesafe.ai: the company site, and the safe place to find official links, including the Discord invite.

If you need the plain-language version of what the model does before any of that, read what Jev is.

Community spaces

  • The official Discord: TypeSafe's server for builders, support, and discussion, with demos surfacing in Show and Tell. Our Discord guide covers how to find the real invite and how to post a build well.
  • X and Reddit: where many builds are first announced. The builders in our directory link their original posts, so follow authors whose receipts hold up.

Lists and directories

  • awesome-jev lists on GitHub: community-curated indexes of tools, SDKs, and projects; the awesome-jev explainer covers what they are and how to use them without mistaking a listing for an endorsement.
  • jevdirectory.org: a website index of tools, guides, and cookbooks.
  • This site: builds with author-reported numbers, all "as reported."

Which list answers which question, including an honest look at what the others do better, is on the directory comparison.

Client libraries

The ecosystem map lives on the API overview, and the TypeScript profile on jev-harness. In short, per ecosystem documentation: official Python and JavaScript SDKs, plus community clients for async Python (jevclient), Swift, and Elixir (req_llm and dedicated clients). All community clients are community-maintained: pin versions and read diffs.

A sane order for newcomers

  1. Skim the official docs' introduction so the vocabulary matches.
  2. Read what Jev is for the mental model: closed questions in, probabilities out, no prose.
  3. Browse the builds here for something close to your problem and read its receipt.
  4. Pick a client from the API overview and run a few hundred of your own examples.
  5. Join the Discord when you have something to show, then submit it.

Frequently asked questions

Where is the official Jev documentation?

At docs.typesafe.ai, which covers the API, concepts, and the official Python and JavaScript SDKs. It outranks every community resource on facts.

Is there a Jev community chat?

Yes: TypeSafe runs an official Discord; the Discord guide explains where builds get posted and how to find the genuine invite.

What is the best list of Jev tools?

For breadth, the GitHub awesome-jev lists; for builds with reported costs, this site. The comparison page lays out the tradeoffs.

Is this site affiliated with TypeSafe AI?

No. shipwithjev.com is independent; for anything official, go to typesafe.ai and its docs.

Numbers throughout are as reported by the build authors, not verified by shipwithjev. Code-shaped examples are pseudocode; the official docs live at docs.typesafe.ai.