Content OS

Token & Activity Analytics

Track what every agent call costs, by feature and operation.

Vertical: Analytics · Status: ✅ Live Back to Analytics · workflows index


Trigger

Written on every tracked LLM call; read from the platform admin dashboard.

Flow

agent call with trackUsage { feature, operation, tenantId, userId }
        |
persisted
        |
admin dashboard: activity + token analytics by feature/operation

What is attributed today

FeatureOperations
feedenrichment
compliancefeed_review - blog_review
blogsdraft_generation - quality_repair

This is the one place the system measures itself well - and it is the control you would use to decide whether a per-tenant enrichment mode should be dialled down.

Agents involved

All three built agents write usage records.

Gaps

Platform-admin only. A tenant cannot see their own consumption.

Roadmap source

Deliverable ⑤ (page 5), partially — see roadmap_ref_extracted.md.

Source: roadmap/workflows/analytics/token-analytics/README.md