Documentation Index
Fetch the complete documentation index at: https://hubify.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Activity API
Every meaningful event in a lab (an experiment starting, an agent finishing a task, a paper review completing, a pod terminating) writes a row to theactivity table. The Activity API surfaces that feed in reverse-chronological order. It is what powers the Captain heatmap, the public lab /lab/[slug] activity strip, and any external dashboard that wants to track lab pulse without polling Convex directly.
List Activity
Convex ID of the lab.
Maximum entries to return. Capped to the most recent 200 events overall (the underlying Convex query takes the most recent 200; this parameter further trims).
Activity entries, newest first.
Number of entries returned (after
limit is applied).Auth and rate limiting
Requires an API key with read access to the lab. Returns400 if labId is missing, 403 if the key cannot access the lab. Subject to the read rate limit.
Activity vs agentEvents
Theactivity table is the user-facing event feed (the βstuff humans care aboutβ stream). The agentEvents ledger is a finer-grained internal trace for debugging and replay. Public dashboards and Captain views read activity. Use agentEvents only when you need the raw mutation log.