Overview
Pensero’s Devin integration helps you understand what AI agents deliver and how their work impacts your engineering organization.
Once connected, Pensero imports Devin activity and aligns it with your engineering delivery data. This allows leaders to compare human and agent contributions in the same context, across code, reviews, delivery, and quality.
Devin is available only on the Enterprise tier.
What You Can Measure
With Devin connected, Pensero helps you understand how agents work alongside your teams, what each contributes, and how to optimize your hybrid workforce for greater delivery and quality.
You can track:
Code and review activity linked to Devin
Devin’s contribution to delivery
The impact of Devin’s work on quality
How Devin’s output compares with human engineering work
This helps leaders move beyond usage tracking and understand the real ROI of AI agents in the engineering organization.
Prerequisites
Before setting up the Devin integration, make sure you have:
Pensero Admin access
Access to your Devin organization
Enterprise tier enabled in Pensero
Permission in Devin to create a service user and assign it a role (Devin organization admin)
Devin Permissions Pensero Needs
Pensero connects to the Devin API with an organization service user that you create in Devin. Pensero only reads data: it never creates sessions, sends messages, or changes anything in your Devin organization.
Grant the service user’s role these three organization-level permissions:
ViewOrgSessions — reads the session list, session details, session insights, and session transcripts. This is what Pensero turns into agent delivery, review, and quality data.
ViewOrgMembership — reads the organization’s users. Sessions only carry a user ID, so this is the only way Pensero can attribute a session to the person who started it.
ViewOrgMetrics — reads aggregate usage and session metrics used in adoption and ROI views.
No write permissions are required. You do not need to grant UseDevinSessions, ManageOrgSessions, or any enterprise-level role.
If your Devin organization assigns membership through an identity provider (IdP) group instead of direct role assignments, contact Pensero support: user attribution may need extra configuration.
How to Set Up the Devin Integration
Step 1: Create a Service User in Devin
In Devin, go to: Organization settings → Service Users.
Create a service user for Pensero (for example, Pensero read-only).
Assign it a role that includes ViewOrgSessions, ViewOrgMembership, and ViewOrgMetrics.
Copy the generated API key. Devin shows it only once.
Copy your Devin organization ID from the same Service Users page. It starts with
org-.
Step 2: Open Devin Settings in Pensero
Go to: Integrations → Devin Settings
You will see the Devin connection page, where you can add or update the credentials for your Devin organization.
Step 3: Add Devin Credentials
Enter the service user API key and the Devin organization ID in Pensero.
Step 4: Save the Connection
Click Save or Update credentials.
Once saved, Pensero validates the credentials and starts syncing Devin activity.
Estimated Devin Cost
Devin does not report what a session cost. Dollar amounts live only in Devin’s own billing screens, and the usage values Pensero can read from the Devin API (ACUs) come back as zero unless your Devin organization is on an Enterprise plan. Pensero therefore estimates Devin spend rather than importing it, so you can still put agent cost next to agent delivery.
The estimate powers two cards on the Agents page:
DEVIN EST. $ — total estimated Devin spend in the selected period.
DEVIN $ / AGENT PT — that spend divided by the delivery points your agents produced in the same period.
Both are labelled as estimates and appear nowhere else: no other cost figure in Pensero includes them.
How the Estimate Is Calculated
Devin labels every session with a size — xs, s, m, l or xl — reflecting how much work it did. That label is the only cost-related signal available outside Enterprise plans, so Pensero prices each session from its size:
xs — $0.00
s — $9.89
m — $9.89
l — $31.94
xl — $73.88
Two other Devin products are added on top: code scan sessions are billed on a separate, cheaper line and count as $3.09 each, and every Devin Review submitted on one of your pull requests adds about $0.02.
These rates were derived by fitting session sizes against one real Devin billing cycle: the fitted total landed within 1% of the invoiced amount for that cycle, with sizes explaining roughly 90% of the daily variation. In that data, s and m sessions were indistinguishable in price and xs sessions were effectively free, which is why they share a rate and xs counts as zero.
What to Keep in Mind
It is accurate at period scale, not per session. Any individual session’s figure is a size-based average, so use the cards to see trends and cost per delivery point, not to audit one session.
The rates come from one organization’s billing cycle. If your Devin contract or usage mix differs, your real invoice will differ from the estimate.
Sessions with no size count as $0. Sessions synced before Pensero began storing Devin’s session insights have no size and do not contribute; contact support if historical periods look too cheap.
All estimated spend sits on the Devin agent identity. It is never charged to the person who started the session or to the author of the reviewed pull request, so it does not distort human cost or delivery figures.
Devin is treated as an agent, not an AI tool. The estimate never appears in AI tool spend, the AI Economics cost figures, or any per-tool usage table.
Requirements
The Devin integration is connected and sessions have synced.
Devin’s identity in Pensero is linked to an agent user. If it is unlinked, Pensero has no agent to attribute the spend to and the cards stay hidden. See Lost and Found.
Estimated Devin cost is released gradually: ask Pensero support to enable it for your organization.
Organizations on Pensero’s Enterprise tier keep their existing ACU-based Devin reporting and do not see the estimate.
Troubleshooting
Credentials rejected, or sync fails with an authentication error: the API key is wrong or expired, or the service user’s role is missing one of the three permissions above. Check the role in Devin, then re-enter the key in Pensero.
Sessions appear but are not attributed to people: the service user is missing ViewOrgMembership, or the Devin user’s email does not match the person in Pensero. See Diagnosing Missing or Incorrect AI Data.
Adoption or ROI views are empty: the service user is missing ViewOrgMetrics.