Jev AI Tools

Community

Contribute a Jev project

This directory stays useful because people put projects into it. There is no account to create and no form to fill in here — submissions go to the upstream list that this site syncs from, which means one submission reaches both places.

This site is an independent third-party directory of Jev AI tools and is not affiliated with, endorsed by, or operated by TypeSafe AI.

Three steps

  1. 01

    Browse what is already listed

    Check the catalog and the eleven category pages first. If your project overlaps an existing entry, say what is different rather than submitting a duplicate.

    Open the catalog →
  2. 02

    Try it before you publish

    Run the pattern you are documenting in the playground so your write-up can describe real behaviour. Anything you publish here should be something you actually ran.

    Open the playground →
  3. 03

    Submit upstream, where this site syncs from

    This directory indexes the community-maintained awesome-jev list. Open a submission issue there — once it merges, the next sync picks your project up automatically and it appears in the catalog and its category page.

    Submit on GitHub ↗

Three ways to help

Add a project

SDKs, integrations, agent tooling, applications, demos, benchmarks, or written-up experiments — if it is built on Jev and publicly reachable, it can be listed.

What to include

  • —Public URL (repo or live site)
  • —One-line description of what it does
  • —Which language or runtime it targets
Open a submission issue ↗

Correct an entry

Stale links, renamed repos, wrong categories, or descriptions that overstate what a project does. Corrections keep the directory worth reading, and they take about a minute to file.

What to include

  • —The entry name or URL
  • —What is wrong with it
  • —The corrected value, if you have it
Report on GitHub ↗

Propose a pattern

Composition patterns on this site describe how to arrange Choice, Score, and Noul for a specific job. If you have shipped one that is not covered, describe the arrangement and the failure mode it avoids.

What to include

  • —The problem it solves
  • —Which primitives are involved
  • —What goes wrong without it
Start a discussion ↗

What a good submission looks like

Include this

  • →A public URL that loads without a login
  • →A one-line description of what it does, not what it might do
  • →The language or runtime it targets
  • →Whether the Jev key is yours to supply (most community tools work this way)

Skip this

  • ×Claims the author did not measure, presented as benchmarks
  • ×Hosted endpoints that require someone else to fund the tokens
  • ×Entries that duplicate an existing project without saying how they differ
  • ×Anything that reads like a landing page rather than a tool

awesome-jev repository ↗

The upstream catalog this directory indexes, including the submission template.

Community Discord ↗

Where builders compare notes, ask about access, and float ideas before submitting.

Official documentation ↗

Primitives, patterns, and the HTTP API reference — link it instead of restating it.