Computer Analytics Links Daily Usage Oversight to Enterprise Reporting
Perplexity’s Computer Analytics separates day-to-day oversight from reporting and planning: administrators can use a daily refreshed dashboard to track organization-wide credit use, top users, connectors, skills, projects, artifacts, and task duration. The company says enterprise customers can use its organization-scoped Analytics API to pull the same usage data into business-intelligence or finance systems, while individual users retain access only to their own activity.
Daily oversight belongs in the dashboard; planning belongs in the API
Perplexity Computer analytics separates two administrative jobs that often get conflated: reviewing usage inside Perplexity and bringing usage data into the systems used for reporting and planning. The dashboard is the direct operational view. It surfaces total credits, active days, average credits per active member, daily credit consumption, a user leaderboard, and activity across connectors, skills, projects, artifacts, and task durations.
The Computer Analytics API is the programmatic route for enterprise organizations that need the same analytics available in a business-intelligence, finance, or internal reporting workflow. The dashboard shows what happened within Perplexity; the API is intended to move that data into the tools where planning decisions are already made.
The distinction matters because dashboard data refreshes once per day. The latest complete picture is therefore typically from the day before, and the dashboard labels its data as UTC and updated daily. Exports can move any dashboard view into a spreadsheet, stakeholder deck, custom analysis, or finance review; the API makes it possible to retrieve the analytics programmatically.
Organization-wide visibility is an admin function
Computer analytics has two access scopes. Individual members and consumer users can see their own activity through Account → Analytics. Organization administrators can open Organization settings → Analytics → Computer to view analytics across all members of the organization.
The organization dashboard is built around measures that make usage visible at more than one level: overall credit consumption, day-by-day changes, member-level ranking, and the tools and work categories associated with activity. A displayed dashboard example includes 127,862 total credits, seven active days, and 18,266 average credits per active member, alongside a credit-usage chart and leaderboard.
| Dashboard measure | What the view provides |
|---|---|
| Credit usage | Daily consumption, with options to group by model |
| Leaderboard | Organization members ranked by credit usage |
| Artifacts | Generated artifacts |
| Connectors | Most-used connectors |
| Skills and projects | Top skills and top projects |
| Task durations | Average task duration |
Only administrators can see organization-wide data. The leaderboard is therefore a way to identify the top Computer users in an organization, including potential power users, internal champions, and people who could form the basis of an internal case study.
The useful dashboard question is not just who spent credits
Daily credit usage is the core monitoring view. Breaking consumption down by day is meant to make spikes, trends, and anomalies stand out more clearly than an aggregate total alone. Administrators can choose seven-, 30-, or 90-day windows, and can group credit usage and created artifacts by the models used.
But credit consumption is only one dimension of the dashboard. It also shows artifacts generated, top connectors, top skills, top projects, and average task duration. Those breakdowns let an administrator inspect the patterns accompanying usage: which connectors or skills appear most often, which projects account for activity, and how long tasks take on average.
The export function supports one-off use outside the product. Any dashboard view can be exported for custom analysis, stakeholder decks, or finance review. Since the data is updated daily rather than continuously, an export reflects the latest full daily picture available in the dashboard.
The API turns analytics into a reusable organization data feed
Enterprise organizations can access Computer analytics programmatically through the Computer Analytics API. An organization admin enables the API from Organization settings → Computer → Analytics and generates an API key. Keys are organization-scoped and can be managed by any organization admin.
The endpoint returns a bucketed time series covering credits, connectors, artifacts, skills, projects, workflows, and task durations. That output can be sent to Snowflake, Hex, Metabase, a spreadsheet, or an internal finance system.
The source presents the API as useful when an organization wants Computer usage data inside an existing reporting or planning process rather than only in a dashboard view or manual export. An internal usage dashboard, for example, can pull in daily credits, top connectors, and task-duration data through an existing business-intelligence stack.
It can also support adoption tracking by team. Comparing Computer usage across departments can show which teams are expanding usage fastest. And historical data can be used for credit planning: the source suggests exporting the previous 90 days and estimating the following month’s needs by member.