Dataset: AI Usage
Entity: AI Usage Measurement
Field ID: actor_type
Type: Select list
Description: The nature of the actor the measurement is attributed to. Possible values are:
HUMANa person.SERVICE_ACCOUNTan API key or service account.AGENTan autonomous agent run.
Source: Calculated
Transformation logic: Calculated from the actor fields the provider populates on a record.
App Mapping
GitHub Copilot | Calculated: always |
Anthropic Claude (coming soon) | Calculated: |
Cursor (coming soon) | Calculated: |
OpenAI Platform (coming soon) | Calculated: |
OpenAI Codex (coming soon) | Calculated: |
Reporting Use Cases
The Actor type field separates people from machines, which matters because agent and service-account usage can dwarf human usage in token terms.
Honest per-developer figures: Filter to
HUMANbefore dividing any measure by a headcount. Service account traffic would otherwise be attributed to whoever owns the key.Measuring autonomous work: Filter to
AGENTto isolate cloud agent and automation runs. The record still carries the person who owns the run inactor_username, so you can attribute autonomous work without a separate field.Explaining token spikes: A sudden jump in tokens with flat interactions is usually agent or API traffic. Grouping by actor type shows it immediately.
