Serves the org-wide recent-activity feed.
Serves the org-wide recent-activity feed. Events are REAL: each recorded run is an invoked (ok) or failed (error) event; each agent's own create/update…
GET /v1/agents/activity
| Address | https://api.hanzo.ai/v1/agents/activity |
| Method | GET |
| Operation | get_agents_activity |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Serves the org-wide recent-activity feed. Events are REAL: each recorded run is an invoked (ok) or failed (error) event; each agent's own create/update timestamps are created/updated events. Merged, newest first, capped. Nothing is invented — an org with no agents and no runs gets [].
Request
GET /v1/agents/activity takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | activityFeed | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
activity | body | activityView[] | — | Activity is the merged run/create/update events, newest first, capped at 50. |
activity[].agent | body | string | — | agent name |
activity[].at | body | string | — | RFC3339 UTC |
activity[].id | body | string | — | ID identifies the event, and its shape says which kind it is: a run event carries the run's own id, while an agent event is the agent id suffixed ":created" or… |
activity[].kind | body | string | — | invoked|failed|created|updated (from real events) |
activity[].message | body | string | — | Message is the line to render, already bounded: "Invoked <model>" for a run that worked, the run's own error truncated to 200 characters for one that did not… |
Failure carries the platform error shape — see Errors.
Examples
hanzo agents activityimport { Configuration, AgentsApi } from 'hanzoai';
const api = new AgentsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getAgentsActivity();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import AgentsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AgentsApi(client).get_agents_activity()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.AgentsAPI.GetAgentsActivity(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, agents_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = agents_api::get_agents_activity(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.AgentsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new AgentsApi(client).getAgentsActivity();curl https://api.hanzo.ai/v1/agents/activity \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches agents through the agents tool, which names its 36 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_agent_conversations"
}
}
}'How is this guide?