Playground/MicroDuck arena
API ACTIVITY

Usage & budget

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
MicroDuck arena

Can a typed choice drive a robot?

Jev sees nine sensor fields and picks one of seven actions per tick. The arena applies it, dents and all.

Closed action set · one request per duck per tick
WORKSPACE GUIDE

MicroDuck arena

Guide a robot through a 3D delivery floor with seven possible actions.

SensorsAllowed actionsRobot movement

What you provide

A simulated arena, sensor state, controller selection, and tick budget. No physical hardware is connected.

What happens

At each decision, Jev chooses from seven allowed actions or the seeded baseline selects locally. Simulation rules apply movement, energy, and collisions.

What you get

Robot movement, delivery and collision counters, telemetry, and decision evidence. Pause keeps the state available for inspection.

Walk through a run

  1. 01

    Explore the arena

    Inspect the simulated robot, delivery stations, and telemetry.

  2. 02

    Choose a controller

    Compare Jev choices with the seeded baseline and set the tick budget.

  3. 03

    Follow the run

    Watch deliveries, bumps, and energy. Pause to inspect each action and its sensor state.

Try this

Run a short seeded baseline, inspect a collision, then compare a Jev run with the same starting conditions.

Execution limits

Simulated hardware only. Each decision comes from seven allowed actions; no physical robot is connected.

Explore the example. Check the evidence.

Arena

JEV ROBOTICS / LIVE SIMULATION

MicroDuck / arena

Preparing the 3D test floor…

STANDING BYTICK 000
Select a robot below to inspect its state
COLLECT CARGO → RETURN TO DOCK0 delivered · 0 dents
Tick 0 · seed 7. Select a duck to read its decisions.
DuckBatteryCargoDeliveredDentsWasted
100%000
100%000
Withheld-sensor test and modelDoubles the requests. The second ask drops these fields from the state entirely.
Step, run, or drive from the arena controls.

What Jev decided

Delivered
0
Dents
0
Wasted
0
Decisions
0
Mean latency
Failed calls
0
SensorsAllowed actionsRobot movement

The arena is still.

Run a tick to see the nine fields the duck sent, the action Jev picked, and what the arena did with it.

One tick costs 2 requests at this setting. Jev never sees the arena, only the fields listed above, and an unusable answer stops the duck instead of guessing a move.