NVIDIA NEMOTRON × NEBIUS TOKEN FACTORY

When the first fix fails,
the agent thinks again.

A recorded two-round incident: real model decisions, real local HTTP checks, bounded actions, and a complete audit trail.

FINAL OUTCOMEHTTP 200Checkout recovered after HTTP 503

MODELNemotron 3 Nano30B A3B · NVIDIA

REAL API CALLS02Both returned HTTP 200

MODEL TOKENS2,038749 in · 1,289 out

SAFETY GATE02 / 02Allowlisted configuration writes

AUDIT REPLAY

Incident sequence

01 / 13

Speed

OBSERVEEVENT 01

Loading verified trace…

DECISION / ACTION—

HTTP CHECK—

AUDIT DATA · SELECTED EVENT

PROVIDER PROOF

Two real responses

Download redacted trace ↗

TRUST BOUNDARY

What this proves

R13 made two genuine Nebius Token Factory requests to nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B. An isolated local HTTP service returned 503 after the first model chosen action and 200 after the second.

This screen replays that historical trace. It makes zero API calls. One successful incident does not establish production reliability.

LIVE execution exists as an operator CLI with a separate Owner authorization, trial readback, request cap, and cost cap. It is not exposed by this web page.