Built with Language integrations

jev_elixir

jev_elixir is a small, idiomatic interface for making typed decisions with Jev. It exposes application-level functions such as Jev.ask?/2 and Jev.analyze/3, while provider adapters handle the external API wire format. The first release supports TypeSafe's System One API and OpenRouter's Decisions API. Both providers support all three System One qu

10 ★ on GitHub

What it is

jevelixir is a small, idiomatic interface for making typed decisions with Jev. It exposes application-level functions such as Jev.ask?/2 and Jev.analyze/3, while provider adapters handle the external API wire format.

The homepage listed on the repository, jev-elixir.hexdocs.pm, puts it like this: Jev — jev_elixir v0.1.0

Getting started

From the README:

def deps do
  [
    {:jev_elixir, "~> 0.1.0"}
  ]

Where the decision sits

jev_elixir calls the hosted decision API rather than running its own weights. That keeps the project small and means its behaviour moves whenever the vendor ships a new model version. It also means an API key and a network round trip sit in the path of every decision.

Models it references: Jev, Alpha, jev.

How active it is

Created 2026-09-21, last pushed 2026-09-21, 10 stars and 2 forks when we read it on 2026-11-02. Everything in this category is weeks old at most, so a stale push date means something different here than it would on a mature project. Check the repository before you depend on it.

Find out what your data actually supports

We turn your historical decisions into a frozen test set, then tell you which model, which threshold, and how much of it you can safely automate.