Usage logs
Who read which skill, when and from which software, refused calls included. Filtering, reading the numbers, exporting CSV.
Every call is recorded, including the ones refused for a wrong, revoked or expired key. This is what answers the questions that emailing files around could never answer.
How far you can see
| Role | Data scope |
|---|---|
| Owner, Admin | the whole business |
| Manager | the people in their own department and in every department below it |
| Member | only the calls made with their own keys |
Members don't get the Member, Department and Kind filters. The page isn't broken; those filters are simply meaningless when you only see your own log.
The four numbers at the top
- Total calls
- With a percentage against the previous period of the same length.
- Denied
- A wrong, revoked or expired key. The number most worth watching.
- Errors
- Calls that failed after authentication had already succeeded, usually a request for a skill that doesn't exist.
- Active keys
- How many distinct keys called during the period. Compare it with the number of keys you issued to see who hasn't started.
Reading the Denied number
A few scattered ones usually mean somebody just switched machines or pasted the wrong thing. But a revoked key being tried over and over means it is still sitting in someone's config, or that it has got out. Click this tile to see the list right away.
Below that sit the Calls per day chart and three rankings: Top skills, Top keys, Top servers.
Filtering
Pick the period from the row of chips: 24h, 7 days (the default), 30 days, 90 days. For your own boundaries, open Custom range and fill in From / To.
- Server
- Only calls into one server.
- Department
- By the department name recorded at the time of the call. Old entries stay correct even after you rename or delete a department.
- Member
- One specific person.
- Status
- OK, Error, Denied.
- Kind
- Skill server (a person reading skills) or AI agent (the management endpoint). Only Owners and Admins get this filter.
- Tool
list_skills,get_skill,get_skill_file,initialize,tools/list,auth, or Other… to type another name.- Search box
- Matches the key name, the detail or the server name.
In the table, click straight on a Key, Tool, Member or Department cell to filter by that value. Far quicker than going back and setting each filter again.
The columns in the table
Time · Kind · Member · Department · Server · Key · Tool · Detail · Status · Duration (milliseconds) · Client · IP. The last two hide on narrow screens.
- Detail tells you exactly which skill or file was read.
- Client is the software that called (Claude Desktop, Cursor…), taken from what the client says about itself. When it can't be identified, the row reads Unknown client.
- Department is a snapshot from the time of the call, not that person's current department.
The log never holds a real key or any skill content
Only the key prefix (the first 8 characters) and the name of the skill. Being allowed to read the log does not let anyone read skill content or reuse somebody's key.
Exporting CSV
The Export CSV button at the top of the page downloads exactly the filter you are looking at, up to 100,000 rows. The file carries a BOM, so Excel on Windows opens accented text correctly straight away, with no encoding to pick.
Every export is written to the system Audit log, because pulling a whole company's usage data out of the product has to stay traceable.
A few real things you can do with it
- Is anybody using the new skill?
- Open that skill → the Usage card → See who read it. A zero after a week means the skill's description isn't clear enough for an AI to know when to reach for it.
- Who has never connected?
- The Member keys page, where the Last used column says Never. Those are the people who need help setting up.
- Is an old key still being tried?
- Filter Status = Denied and look at the Key column.
- Which department uses it most?
- The dashboard of the business already carries a Calls by department table for the last 7 days.
How long logs are kept
90 days by default, set by whoever runs the system (System settings → Keep usage logs for (days)). Rows older than that are purged automatically, once a day. If you need them longer for reconciliation, export CSV on a schedule.