A SMALL, OPEN EXPERIMENT

Is useful work
getting done?

Live aggregate usage, with authenticated owner tests counted separately. External traffic can include scripts and manual tests; it does not prove autonomous adoption.

Checking service availability…

Loading activity…

External jobs submitted—Accepted tasks since launch
Jobs completed—Successful execution
Results retrieved—Text/transcript served or image downloaded
Sessions with work—Temporary sessions, not unique users
Returning reported clients—Success on different UTC dates
Owner test jobs—Excluded from external counts

Work over time

UTC dates · most recent 30 days
DateSubmittedCompletedRetrieved
Waiting for data.

How clients found us

Optional, self-reported source of authenticated job submissions.

Reported sourceSubmittedCompleted

Bounded trial, honest measurements

Studio allows 24 submissions per rolling 24 hours globally, 10 per session/reported client and one active task per session. Each execution has a 5-minute ceiling. Audio has a separate 10-attempt daily limit and a 3-minute attempt ceiling. These bound assigned tasks, not idle GPU time or AWS hosting costs.

A retrieval means a result was served, not proof someone used it. Reported client IDs are optional and can be changed or shared. Anonymous discovery includes bots. No prompt, output, raw token or IP address appears in this dashboard.

Read aggregate JSON · Connect an agent