Computer Usage Analytics - Perplexity
Summary
The Perplexity Computer Usage Analytics API provides organizations with detailed, bucketed usage data for their computational resources. Accessible via the https://api.perplexity.ai/v1/analytics/computer/usage endpoint, it requires a specific organization analytics API key, distinct from a regular Sonar API key, generated by an organization administrator. Users can query various datasets, including credit_usage, connectors, artifacts, skills, spaces, workflows, and task_durations, specifying start_time, end_time, and bucket_width (1d or 1h). The API returns chronological usage data, such as a count of 350 for a given period, broken down by_category into "paid" (250) and "promo" (80), with pagination support for larger data sets.
Key takeaway
For MLOps Engineers or platform administrators managing Perplexity resources, integrating with the Computer Usage Analytics API is crucial for cost management and operational visibility. You can programmatically monitor credit_usage and track resource consumption across connectors, skills, and workflows to optimize spending and identify usage patterns. Implement automated alerts based on task_durations or specific dataset usage to proactively manage your organization's computational footprint and ensure efficient resource allocation.
Key insights
Perplexity offers an API for organizations to monitor detailed computer usage analytics across various datasets.
Principles
- Organizational analytics require a dedicated API key.
- Usage data is bucketed by time and category.
- Query windows are limited to 90 days.
Method
Query the analytics/computer/usage endpoint with an organization analytics API key, specifying dataset, start_time, end_time, and bucket_width to retrieve chronological usage data.
In practice
- Track credit_usage for billing reconciliation.
- Monitor connectors and skills adoption.
- Analyze task_durations for performance insights.
Topics
- Perplexity API
- Usage Analytics
- API Key Management
- Resource Monitoring
- Cost Optimization
- Data Bucketing
Best for: CTO, VP of Engineering/Data, Director of AI/ML, Software Engineer, AI Engineer, MLOps Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by perplexity.ai via Google News.