Loading

Turning Jev On and the Console

Jev sends nothing until it is switched on with an API key. The TypeSafe Jev console shows whether it is ready, proves the connection, and lists the calls your features have made and their cost.

Where to find it

Architect Panel → Activity:

  • TypeSafe Jev — status, Check connection, Test call, the Playground and Recent Jev runs
  • AI Usage — every Jev call with its cost, listed under the service TypeSafe Jev
  • AI Run Log — the run rows themselves, read-only

Architect Panel → Configuration:

  • AI Settings — the TypeSafe Jev section of the AI configuration file
  • Platform Modules — the AI module, which hides the console when switched off

Switching it on

Jev's settings live in the installation's AI configuration file, the same file the AI gateway uses. Only two are required.

  1. Get an API key from TypeSafe for this installation, under an organisational account rather than a person's.
  2. Set it. Open AI Settings, go to the TypeSafe Jev section, tick Switched on, paste the key into API key and click Save. If the screen says This screen cannot change the file, ask your hosting administrator to set the same two values in the AI configuration file.
  3. Open the TypeSafe Jev console and check that the Status card shows Ready to call: Yes.
  4. Click Check connection. It asks TypeSafe which models your key may use. It is free and is not logged, so it proves the key and the network path without spending anything.
  5. Click Test call. It sends one small fixed request: a customer message and three questions, one of each type. It is a real, billed call of about 450 input tokens, logged as admin.testcall.

The other settings

All optional; the labels are those on AI Settings.

  • Model: blank means jev-latest. That and jev-preview are aliases that follow TypeSafe's releases. Once you have tuned a confidence bar against a version, pin it, for example jev-1.13.0.
  • API address: blank means TypeSafe's own. Set it only to send calls through a proxy, and give the host only, with no /v1. The console never shows it.
  • Timeout (s) and Retries: per attempt. Inside a page request Jev gets 10 seconds an attempt, one retry and 15 seconds in all; background work gets 30 seconds and two retries, unless a feature sets tighter limits of its own. These settings can lower the page figures but never raise them.
  • Calls per web request (100) and Seconds per web request (30): ceilings for one page request.
  • Input price and Output price: used only for the run log's cost estimate.
  • Playground on the Jev console: untick to hide the playground and refuse its calls.

The messaging threshold and the three Feed Queue settings are covered with those features.

Reading the Status card

The card is read-only and never shows the key or a custom address. Ready to call is Yes only when Jev is switched on, has a key and has a usable address; when it says No, nothing is sent and every feature behaves as though Jev were unavailable. AI budget: Checked means the budget is asked before every call, and Run logging: Off means calls are made but not recorded.

When the test call fails

A failure shows a code and a hint:

  • not_configured: switched off, no key, or an API address that is not an http(s) URL. Nothing was sent.
  • auth: TypeSafe refused the key. HTTP 403 means no key reached it; 401 means a key it does not accept.
  • not_found: with HTTP 404 the API address is wrong (it must not end in /v1); otherwise TypeSafe does not know the model named.
  • timeout or connection: check that the server can make outbound HTTPS calls to TypeSafe, through any proxy and DNS.
  • rate_limited, overloaded or provider_error: TypeSafe is busy or failing. Try again shortly.
  • budget_exceeded: the AI budget refused the call, so nothing was sent.

Cost, the run log and the AI budget

Every Jev call writes one row to the AI run log, with any retries counted in that same row. The feature column says what asked: admin.testcall, jev.playground, workflow.decide, messaging.condition or erpfeed.suggest. The Recent Jev runs card lists the latest ten for your account, with When, Feature, Outcome, Model, input tokens, Cost and time taken; Open shows a run in AI Usage, and All Jev calls in AI Usage opens the last 30 days.

Each decision is individually very cheap, so costs are shown to six decimal places. One row's figure is approximate; totals over many runs are reliable. Failed calls and budget refusals are recorded at zero cost. While Jev is switched off nothing is sent and nothing is recorded.

The AI budget is checked before every call. A refusal sends nothing and is recorded with the code budget_exceeded. The run log keeps Jev's answers but not what was sent, unless Keep the request is on in the run log section of AI Settings. Usage, credit and budgets in general are covered in AI Usage & Run Log and AI Credit & Spend Limits.

Worked example

An architect opens the console on a new installation and sees Ready to call: No, with a warning that Jev has no API key. They save the key in AI Settings, reload, and Check connection lists the models the key may use. The test call answers all three questions and appears in Recent Jev runs. Only then do they build the first workflow step that relies on Jev.

Recommendations

  • Make the first call yourself, rather than letting a live feature discover a bad key.
  • Use Check connection after any change to the key or address: it costs nothing.
  • Pin the model once a bar has been tuned against it.
  • Check Recent Jev runs weekly at first: a run of errors means a feature is quietly falling back.