Devin
Antenna automatically tracks Devin usage from Cognition’s Devin Enterprise API. Get insight into who is using Devin, how much agent work they run, and how that consumption trends across your enterprise.
Devin measures agent work in ACUs (Agent Compute Units) rather than autocomplete or code-suggestion activity. Metrics such as suggestion acceptance rate or percentage of code written by AI are not available for Devin.
Prerequisites
- A Devin Enterprise account with permission to create service users in enterprise settings
- Admin access to your Antenna enterprise
Setup
Create a Devin service user
- In Devin, go to Enterprise settings > Service users.
- Click Create service user and give it a descriptive name, such as
Antenna Analytics. - Assign it an enterprise role that includes the ViewAccountMembership and ViewAccountConsumption permissions. Add Use Local Analytics API to also collect model-level desktop usage.
The service user must be created at the enterprise level. Organization-scoped service users cannot read the enterprise membership and consumption endpoints Antenna uses.
Generate an API key
Click Generate API key on the service user and copy the key — it starts with cog_ and is only shown once.
Connect in Antenna
- Go to Settings > Sources > Add source in your app.antenna.dev account.
- Find Devin and click Connect.
- Paste your API Key.
- (Optional) Enter an API URL if you run a dedicated Devin deployment, for example
https://api.acme.devinenterprise.com. Leave it blank to usehttps://api.devin.ai. - Click Connect.
Antenna validates the API key when you connect, so an invalid key or one missing the required permissions is rejected immediately. After connecting, Antenna backfills your historical consumption and then refreshes data every two hours.
Data collected
We pull from the Devin Enterprise API (v3) and the Devin Desktop analytics API:
| Purpose | Endpoint |
|---|---|
| Enterprise members | GET /v3/enterprise/members/users |
| Enterprise daily consumption | GET /v3/enterprise/consumption/daily |
| Per-user daily consumption | GET /v3/enterprise/consumption/daily/users/{user_id} |
| Daily desktop usage by model | GET /api/v2alpha/analytics/consumption |
For each member we store their name, email, enterprise role, and the date they joined the enterprise. We use these to match Devin users to Git users so Devin activity appears alongside the rest of your delivery data.
For each day we store total ACUs plus a breakdown by product (Devin, Cascade, and Terminal), both for the enterprise as a whole and per user. Devin buckets consumption on a midnight Pacific boundary, so a day in Antenna matches the same day in Devin’s own reporting.
Desktop usage by model
The consumption endpoints report ACUs per product, but not per model. To show which models your developers run, Antenna also collects daily Devin Desktop usage broken down by user, model, and IDE. For each combination we store the credits or ACUs billed and the number of messages sent.
This data comes from a separate analytics API, so it requires the Use Local Analytics API permission on your service user, and it is not available for dedicated Devin deployments. The rest of your Devin data is collected either way.
Antenna does not collect prompts, session transcripts, or any other content from your Devin sessions.
Resources
- Devin Docs: Enterprise API quick start
- Devin Docs: List enterprise users
- Devin Docs: Daily consumption by user
- Devin Docs: Desktop consumption analytics