$JEWZER · Runtime v2 · us-west + eu-central

Your agents act.
Jewzer writes down
every reason why.

Point an agent at Jewzer and Jewzer becomes its runtime. Every answer, every tool call and every turn it decided to skip lands in an append-only log with the reasoning, the confidence and the latency attached. The agent works inside the policy you wrote. It has no way to edit the record.

The tape Live 219 MS PER ANSWER
TRIAGE closed 47 tickets Act
confidence 0.37 · under review threshold38s ago
Decisions logged
266.63M
append-only since March
Tool calls
4.990M
312 blocked by policy
Agents
12
11 in production
Median latency
219
ms, p50 across all agents
Explore

Agents running now

+ Deploy an agent
AgentModel5mDecisions MedianTool callsBlockedStatus
Mechanism

What happens to a decision

01

The turn is captured

Before the model runs, Jewzer snapshots what the agent can see: the prompt, the retrieved context, the tools the policy allows this turn and the budget left. That snapshot is written first, so a decision can be replayed even if the run fails.

02

The agent answers

The model picks one of four moves and states its confidence: act, call a tool, wait for more signal, or halt. Anything under your review threshold goes to a human instead. Median time to an answer is 219 ms.

03

The record is sealed

The move, the reasoning, the tool response and the latency are appended to the log and hashed against the turn before it. Records cannot be edited or removed, by your team or by ours. Export the chain whenever you want it.

Plate 01 One column per decision, newest right · row = confidence × 10 actwaithalt
Live

Every answer, as it happens

4.6 answers a second · us-west
SEALED RECORDS
The obvious questions

Can the agent go off-script?

Can an agent do something you didn't approve?
No. Each agent runs against a policy you write: the tools it may call, the arguments it may pass, the spend per turn and the confidence it needs to act alone. The runtime enforces the policy outside the model's context. The agent cannot read it, argue with it or edit it.
What if an agent never acts?
Waiting is a logged decision like any other, with its own reasoning and confidence. If an agent waits past the timeout you set, the turn escalates to whoever owns the queue and the escalation is recorded too. Nothing expires silently.
What does an agent actually see?
The turn snapshot, which you can open on any record: the prompt as sent, the retrieved documents with their scores, the tool schemas available that turn, and the remaining budget. If the answer looks wrong, this is usually where the reason is.
Who can delete a record?
Nobody. Records are appended and hashed against the previous turn, so removing one breaks the chain for everything after it. You can redact field values on request and the redaction is itself a record. Support cannot quietly rewrite your history.
+ Deploy an agent with $JEWZER