JevMade Sign in
← Back to experiments

Benchmarks & research

jev-measured

Measures what the live Jev API actually returns across eight realistic use cases, reporting cost, latency and response shape rather than rate-card arithmetic.

Bookmark: jev-measured Keep this in your collection.
Leave a noteWhat would you try with this? : jev-measured

Only you can see your notes.

Source screenshot of jev-measured
SOURCE SCREENSHOTFull screenshot ↗

What it does

Three results a builder should know: a real decision costs $0.0000153–$0.0000226, Score returns a probability-weighted rubric index rather than a 0–1 float, and Noul carries no confidence field.

How you can use it

When planning an AI feature, use the recorded examples to estimate how message length affects your bill. Ask your developer to group questions about the same message into one request, rather than pay to send it repeatedly. For speed comparisons, measure internet travel time separately. The numbers here describe one machine's connection, not the waiting time your users will see.

Maker-reported (not independently measured by JevMade): rag-reranking 364 input tokens, cost $0.0000153; support-ticket-triage 539 input tokens, $0.0000226 · Pricing is $0.042 per 1M input tokens with no output tokens billed · Raw wall-clock medians 458-563 ms; measured TCP handshake floor median 198.8 ms (7 samples, 191.2-266.4 ms)

Primitives
choice, score, noul
Platform
Python
Added
Project created

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.