JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Measured integration report

I put TypeSafe's Jev in front of Grok Build and it got 22 to 40% cheaper on the same tasks

Nitro uses one Jev call to trim Grok Build’s tool schemas for a whole turn. The author reports lower token costs on small coding tasks, but no convincing wall-clock speedup.

Original by DanAgent workflowsX articleOriginal published Source reviewed

Before you dive in

What you’ll find in the original

  1. Keep core workspace tools and their dependencies available, and fall back to the full tool list on a routing failure.
  2. Hold the chosen schemas stable across a turn so the model’s prompt cache can reuse its prefix.
  3. Measure whole-task cost and latency separately; the tested long generation dominated wall-clock time despite the smaller menu.
Worth knowing

The 22–40% savings come from two runs per cell on three author-selected tasks, not a broad benchmark. A tool wrongly excluded for a later step could break an untested task; JevMade did not rerun the experiment.

More guides →See the experiments →