Who it is forA team already using a Jev client that wants to run the models on its own hardware.
The problemChanging the client code for a new model host costs time and risks breaking working integrations.
The outcomeThe existing client gets decisions from the local server after only the base URL changes.
What you need first
- Python with pip and git installed
- A GPU with enough memory for the chosen model, or an Apple silicon Mac for the MLX builds
- A 96 GB GPU if you want to serve the 27B model
Steps
- Start the server with
rsi-jev serve v6.1-vl-4b --effort auto --port 8000 - Set the Jev client's base URL to http://localhost:8000 in its configuration (inferred, check the README)
- Keep the model name as jev-latest, as shown in the quickstart request
- Send one request through the client and check that the response includes the layer and confidence
Prompt for your agent
Given an existing Jev client in <project-path>, point its base URL to localhost:8000 after running `rsi-jev serve v6.1-vl-4b --effort auto --port 8000` from the Shanghua-Gao/RSI-Jev repo. Run one existing client request and return the response. Verify that the client works with no other code changes.
Caveat. The README says an existing Jev client works once its base URL points here, but it does not list which client features are covered, so test your own calls first.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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