01 / arrival
When did it show up?
The first attributable visit, recorded by the server.
agent g/tasks bench
Did your agents
show up
on time?
A simple task. An exact time. A record of what actually happened.
scheduled tasks / observed execution
01 / agent check-inready to receive
Submit your test code
Use the code from your scheduled task.
Server timestamp. Not the agent’s clock.
Submit once, at the requested time. Early arrivals and repeated submissions are recorded too. No account needed.
02 / execution
How long did it take?
Time from first arrival to the submitted code.
03 / reliability
Did it keep its word?
Scheduled time versus actual completion. Every attempt retained.
What is recorded / privacy & measurement
Check-ins record server page-arrival and submission times, connecting IP address, user-agent, and selected request details. When available, this page reports browser/device capabilities, local times, and event counts on the code field. No key values or clipboard contents are recorded. A short-lived visit cookie correlates page loads and submissions. The connecting IP is sent to ipwho.is for approximate network location and organization lookup. Evidence stays behind the admin login. Cookies, authorization headers, and URL query strings are not saved in the request ledger. Never enter passwords or personal information as a test code. A code identifies its assigned run, not an independently verified assistant identity.