Playground/Agents & workflows/Ask gate
API ACTIVITY

Usage & budget

PLAYGROUND SAFETY LIMITS

Steady requests. Visible limits.

0 active · 0/20 queued

Browser: one start every 1.2 seconds (at most 50/minute), up to 2 active calls and 20 waiting. Shared by examples in this tab. Waiting requests cancel when their run is stopped; a full queue rejects new work without an API call.

Server: 60 requests per rolling 60 seconds and 2 concurrent calls per key, per server instance. Other tabs using the same key share that instance’s allowance. This in-memory safeguard resets on restart and is not a distributed or account-wide quota.

Source: playground policy in lib/requestRateLimit.ts. TypeSafe may impose separate limits. Provider HTTP 429 pauses calls until its reported reset; without a reset time, retry requires your action. HTTP 402 is a budget/billing failure, not a pacing limit. No automatic retries or background replay.

Your TypeSafe API key

Import your key to override the shared server default.

Saved on this browser until removed or site data is cleared. Masked on screen; sent only with Jev requests through this app. The saved value is never displayed.

Connecting
Ask gate

Ask Jev, or ask a human?

Check official TypeSafe docs first. If they do not resolve it, check community context before asking a person.

Classification only · no answers written
WORKSPACE GUIDE

Ask gate

Decide whether a request belongs with Jev or needs human attention.

QuestionEvidenceReview decision

What you provide

An incoming question or chat dump, conversation history, and optional documentation that could support an answer.

What happens

Jev classifies whether the supplied evidence can support the question. Citation checks and conservative policy control the final routing decision.

What you get

An evidence-backed gate decision with supporting citations, or a human handoff when support is weak. No answer or message is sent.

Walk through a run

  1. 01

    Supply the evidence

    Enter a question with conversation history and optional documentation.

  2. 02

    Run the gate

    Triage one question or a whole chat dump.

  3. 03

    Check the citation

    Inspect the supporting message or document. Weak evidence goes to a human.

Try this

Run the sample with its supporting documentation, then remove that evidence and compare the handoff decision.

Execution limits

Live classification only. The lab does not write an answer or contact a reviewer.

Explore the example. Check the evidence.

What came in

The question is gated on its own. It does not need to appear in the transcript below.
Only the last 20 messages are sent as context.Official TypeSafe docs are retrieved automatically. Add optional local notes here. One line per fact. Headings starting with # name the section a citation points at.
Parsed context 4 messages · 0 doc lines
Val

Every Jev call in this playground goes through /api/run, so TYPESAFE_API_KEY stays server-side. Never ship it to the browser.

Morgan

Same on Vercel: add TYPESAFE_API_KEY as a project environment variable and redeploy. No NEXT_PUBLIC_ prefix, ever.

Priya

Rate limits are 60 requests a minute per key. Go over and you get HTTP 429 back; the playground shows it as a plain error and you retry.

Val

And leave the model field empty if you want jev-latest, which is the default.

Official docs → community context → human

Every run reads TypeSafe’s full documentation first (cached for 10 minutes). If unavailable, it follows relevant pages from the docs index. No API key is needed to retrieve docs.

Model
Docs first · up to 2 Jev requests

The gate

QuestionEvidenceReview decision

Does this really need a person?

Run triage to see whether the channel or the docs already answered it, with the exact line that proves it.

Gate more questionsTrust a person

Jev only picks one of four outcomes and one piece of evidence. Any weak or unsupported match falls back to a human.