Playground/Code & governance
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

TYPESAFE AI / CODE & GOVERNANCE

Typed judgments.
Code has the last word.

Surface risky changes and verify decisions against fixed rules.

Change or constraintTyped questionsRule-checked verdict

Jev chooses inside a fixed set.
Code decides what that choice may do.

Workspaces4

Open one to try it. Every workspace keeps mock, live and failed results clearly labeled.

PR review

Paste a PR or diff to separate routine changes from hunks needing review.

in
Diff
out
review gate

Proposal review

Let an agent propose one patch, ask Jev four questions about it, and let code decide.

in
Proposal
out
code verdict

AST governance

Trace changed symbols, affected callers and deterministic policy findings.

in
Symbols
out
change impact

SMT solver

Compare Jev’s prediction with an exact solver on structured constraints.

in
Constraints
out
verified result