Settings

Add your own TypeSafe key here to run anything. It is saved in this browser only, so a key added on one machine or one domain does not follow you to another.

Where your key is kept

Whatever you enter here is stored in your own browser and attached to each request as a header. This server holds it for the length of one request, never writes it to disk, never puts it in a database and never logs it.

Being straight with you about the limits: the key does travel to this server, because that is how it reaches TypeSafe. Anything in browser storage can also be read by script running on this page. If neither is acceptable, run it locally — that is what it was built for.

TypeSafeRequired

console.typesafe.ai

Required. Every semantic judgment on every page is answered by Jev. Without a key, nothing runs.

Charged on input tokens only, at $0.042 per million. A page costs roughly 4,000 tokens — about a hundredth of a penny.

not set

Powers every semantic judgment. Create one at console.typesafe.ai.

not set

Leave blank to track jev-latest. Pin a version such as jev-1.13.0 if you have tuned thresholds against it.

DataForSEOOptional

app.dataforseo.com/api-access

Optional. Fetches the live top ten for your target query so Jev can judge format, coverage and differentiation against what actually ranks. Everything else works without it.

About $0.002 per lookup, then cached for 24 hours so re-running costs nothing. Testing the connection here is free.

provided by host

The email address you sign in to DataForSEO with.

provided by host

The API password from your DataForSEO dashboard, not your account password.

Running your own instance

Keys entered above always win. On an instance you host yourself you can also supply a fallback for everyone, as environment variables or, when running locally, in .jevseo.local.json in the project root. That file is gitignored, owner-only, and never leaves the machine.

vercel env add TYPESAFE_API_KEY
vercel env add DATAFORSEO_LOGIN
vercel env add DATAFORSEO_PASSWORD