DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run existing TypeSafe Jev API code against localhost with Rizzo Flow

Change one URL so code written for the TypeSafe API calls a local model instead.

Who it is forA developer whose app already calls the TypeSafe Jev API and who wants to test it offline or avoid hosted calls.

The problemHosted Jev calls cost money per use and send data to a closed service, which blocks some local or private testing.

The outcomeYour existing Jev-style code returns decisions from a model on localhost after a one-line base URL change.

What you need first

  • Python 3.11 or newer
  • git
  • uv (https://docs.astral.sh/uv/)
  • About 4.4 GB of free disk space for the default 4B model, plus the llama.cpp runtime (about 11 MB on a Mac, 30 MB with Vulkan, about 570 MB with CUDA)
  • A machine that can run llama.cpp: an Apple, NVIDIA, AMD or Intel GPU, or no GPU at all

Steps

  1. Set up the server by running uv sync --locked, uv run rizzo download and uv run rizzo serve from the Rizzo Flow folder.
  2. If you need Bearer auth on the Jev-compatible endpoints, set RIZZO_API_KEY before starting the server.
  3. In your app, change the TypeSafe API base URL to http://127.0.0.1:8017.
  4. Run your existing tests or a sample call and compare the returned decisions with your expected results.
  5. Note that the base model answers 'cannot determine' often with abstention on, so the Jev-compatible endpoint always disables abstention.

Prompt for your agent

In the rizzo-flow repo, start the server with `uv run rizzo serve`, then point the existing TypeSafe API client in <path-to-app> at http://127.0.0.1:8017 and run its test suite. Return the failing or passing tests. Verify that each decision response has the same shape the client expects.

Caveat. Rizzo Flow is not affiliated with TypeSafe and does not reproduce Jev's architecture, so expect different answers and probabilities from the hosted service.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page