logoalt Hacker News

tgluck • today at 12:06 PM • 4 replies • view on HN

Author here. This puts a proxy in front of repeated Jev classification calls. At first everything goes to Jev; from Jev's answers it trains a small head on frozen sentence embeddings, picks a confidence threshold with an exact finite-sample bound so that at most 2% of all requests get an answer Jev wouldn't have given, and then answers the confident share locally at ~15 ms on a CPU. A permanent 2% audit keeps checking; if agreement breaks, everything falls back to Jev and it retrains.

Known limits: agreement is not accuracy (if Jev is wrong, so is the local model); coverage tracks how consistent Jev itself is (22% on noisy tweet tasks, 80% on news); it speaks Jev's API only, an OpenAI-compatible front is on the roadmap. Since 0.4.0 the guarantee can also cover "would Jev have been unsure", which matters if your code routes low-confidence answers to review. Apache 2.0.


Replies

kodefreeze • today at 5:02 PM

Isn't this against their ToS? Useful for hobby stuff.

➕ show 1 reply
dotancohen • today at 5:49 PM

It would be great if we could correct Jev's incorrect answers, even on a separate endpoint. Let me tell it what Jev got wrong.

What type of head is that? What type of model is that head part of?

➕ show 1 reply
ricardobeat • today at 9:50 PM

Please don’t post AI generated replies.

➕ show 1 reply
wedg_ • today at 4:29 PM

Woah cool idea. So it's almost a drop-in replacement for a typical Jev setup that just reduces your jev bill over time ?

➕ show 1 reply