Skip to main content

Activity & Analytics

Once agents are working against your content, two questions come up. apistash answers them in two different places, because they are different questions:

  • What are my agents actually doing? → Activity.
  • What of my content is nobody using? → the content lists themselves.

Activity​

Activity in the dashboard has three tabs — Tools, Prompts, Resources — and all three answer the same question over the same rolling 30-day window: what was used, and how often.

  • Tools lists every tool that was called, with the number of calls, how many succeeded, how many failed, and the resulting success rate. Open a tool to see its individual calls: when, with which credential, how long it took, and the error if it failed.
  • Prompts and Resources list every customer-owned item that was read, how often, and when it was last read.

Because the window rolls, activity older than 30 days is not shown. A tool that was busy two months ago and idle since appears nowhere on these screens — which is the point: they describe the present, not the archive.

Whose activity you are looking at​

Tool calls and reads are grouped along different lines, and it is worth knowing which:

  • Tool calls are grouped by whose allowance they counted against — your own, or the organization's.
  • Reads are grouped by who owns the prompt or resource that was read, no matter who triggered the read.

That gives each screen a different reach:

WhereToolsPrompts & Resources
Activity in your personal workspaceYour own calls outside any organization.Reads of the content you own — including your private content inside an organization.
Mine in an organization's ActivityYour own calls inside that organization. Only you can see them.—
Organization in an organization's ActivityCalls made with the organization's own API keys and machine-to-machine OAuth clients — work done as the organization. A member's own calls live under the Mine scope.Reads of the organization's shared content, whoever triggered them.
Activity in a team—Reads of that team's prompts and resources, whoever triggered them.

Platform prompts such as apistash/agent-doctor have no customer owner and create no Prompt Activity entry. Their reads still use the prompt-read rate limits; the Doctor's subsequent list_agents and get_agent calls appear as ordinary tool usage.

So a colleague reading a prompt from your organization's catalogue shows up in the organization's figures, not in theirs — the read belongs to the content, not to the reader.

The organization view covers your shared content — the organization catalogue plus team-owned items. Members' private items inside the organization, and the reads of those items, stay visible only to the member who owns them, in that member's own personal workspace. Nothing you keep private surfaces in an organization-wide report.

On the organization and team screens, Recent reads additionally shows the individual reads newest-first, each with the person, API key, or OAuth client that triggered it.

Seeing the Organization scope requires the corresponding permission; team Activity requires it on that team. The Mine scope always belongs to you. See the access model.

Finding content nobody uses​

The opposite question — which of my prompts and resources is dead weight? — is answered where you manage that content, not in Activity:

  • In your Prompts and Resources lists, an item that was not read in the last 30 days carries a Never read badge next to its name. When everything is being used, you see nothing — the badge only appears when there is something to look at.
  • Open an item and its details show Reads (30 days) and Last read.

"Never read" means not read in the last 30 days, not never read since it was created. An item that had its moment last quarter is flagged too — and that is usually what you want to know when you are deciding whether to keep, rewrite, or delete it.

This pairs naturally with managing your content: when a prompt turns out to be unused, you can have your agent rewrite or retire it in the same session.

Next steps​