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

How to ask JEV questions about objects from a live RGB-D camera with JEV Sees

Feed RGB and depth frames into a loop and ask JEV about detected objects with 3D positions.

  • Research
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Authorization notice. JEV Sees is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Keep the JEV API key in your environment and out of the camera script you share with others.

Who it is forA robotics developer whose camera publishes RGB and depth frames and who needs answers about objects that include metric positions.

The problemConnecting a live depth camera to a visual question model usually needs custom glue code for object positions and per-frame answers.

The outcomeA running camera loop that prints JEV answers for each observed object, with distances when camera intrinsics are provided.

What you need first

  • Python 3.10 or newer
  • A JEV API key from console.typesafe.ai/keys
  • Internet access for the first run, unless the Florence-2 and CLIP weights are already available locally
  • Git and a terminal

Steps

  1. Clone the project with git clone https://github.com/CharlesFeng0314/JEV_sees.git.
  2. Enter the folder with cd JEV_sees.
  3. Install it with python -m pip install -e ..
  4. Set your key on macOS or Linux with export TYPESAFE_API_KEY="your-key", or in PowerShell with $env:TYPESAFE_API_KEY = "your-key".
  5. Write a loop that reads RGB and depth frames from your camera and calls observe(rgb, depth, intrinsics=...), then passes the returned objects to ask(...) with your question. (inferred, check the README)

Prompt for your agent

In the JEV_sees repo at <repo path>, write a camera loop that calls observe(rgb, depth, intrinsics=...) on each frame from <camera source> and then ask(...) with the question What is this object? Expect printed JEV answers per object; verify that objects include 3D positions or distances when intrinsics are supplied.

Caveat. The README mentions observe and ask only briefly without full signatures, so confirm the exact call format in the source before relying on it.

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