Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

The agent sends a research goal, requested platform, and the supported workflow list to Jev. Jev returns one Choice route among Instagram, TikTok, LinkedIn, or unsupported; validation checks the closed route schema and rejects an unsupported route or conflict with an explicitly requested platform. The selected route then determines a bounded local read-only socai search; Nebius can synthesize a source-linked brief afterward.

What Jev decides

Social research routeExample answers · not a recorded Jev response · Source ↗
Question 1 · route
YOUR APP
INSTRUCTION

Choose one supported read-only search workflow, honoring an explicit platform; otherwise return unsupported.

STATE

A supplied research goal, requested platform (including auto), and three supported read-only platform workflows.

JEV · CHOICE
  1. instagram_search
  2. tiktok_search
  3. linkedin_search
  4. unsupported

App workflow

  1. Route the goal

    Send the goal and platform constraint to Jev; validate the returned route and confidence.

  2. Run bounded search

    Map the accepted route to a fixed local socai search command; collect capped output from the existing browser session.

  3. Project evidence

    Filter URLs and project only approved public fields from the CLI results.

  4. Synthesize report

    Optionally send projected evidence to Nebius for a source-linked brief; output identifies synthesis as unverified model output.

Why it is interesting

It draws a narrow boundary between model inference and browser execution: Jev chooses only a typed route, while fixed local command construction and validation control what can run.