openrouter-analytics-schema

Identify valid query parameters for OpenRouter analytics API requests.

209|33|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/OpenRouterTeam/skills --skill openrouter-analytics-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openrouter-analytics-schema
Source: https://github.com/OpenRouterTeam/skills/tree/main/skills/openrouter-analytics-schema
Command: npx skills add https://github.com/OpenRouterTeam/skills --skill openrouter-analytics-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of building OpenRouter analytics queries by providing a single, always-up-to-date reference for all available query parameters, so you never have to guess at valid metrics, dimensions, or filters or deal with rejected API requests due to invalid query structures.

Core Features & Use Cases

  • Complete Schema Reference: Access full definitions of all queryable analytics metrics (categorized as volume, cost, performance, and efficiency), dimensions, filter operators, and time granularities, including time range limits for specific data points.
  • Natural Language Mapping Guide: Use built-in pattern matching to translate common business questions like "What is my cache hit rate by model?" or "How much did I spend on web search last week?" into the correct metric, dimension, and filter combinations.
  • Filter Value Reference: Get clear guidance on where to find the correct underlying IDs for label-resolved dimensions like API keys, users, and workspaces to avoid empty query results.

Quick Start

Use the openrouter-analytics-schema skill to look up the correct metrics and dimensions for your question about OpenRouter API spend broken down by model and country.

Frequently Asked Questions about openrouter-analytics-schema

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build valid OpenRouter analytics queries without getting invalid parameter errors?

Building valid OpenRouter analytics queries requires correct query parameters for metrics, dimensions, filters, and time granularities. This Skill provides a complete schema reference to eliminate invalid parameter errors and ensure accurate API requests.

What metrics and dimensions are available for the OpenRouter analytics API?

OpenRouter analytics API metrics are categorized into volume, cost, performance, and efficiency. Dimensions and filter operators allow you to break down usage, spend, and latency data by model, API key, user, and workspace.

How do I map natural language questions to OpenRouter analytics metrics and dimensions?

You can map natural language questions to OpenRouter analytics metrics and dimensions using built-in pattern matching. This translates queries like "What is my cache hit rate by model?" into the correct metric, dimension, and filter combinations for your API request.

Why are my OpenRouter analytics queries returning empty results for API keys and users?

OpenRouter analytics queries return empty results when using label-resolved dimensions like API keys and users without the correct underlying IDs. You must reference the exact filter values to avoid empty query results and retrieve accurate data.

Are there time range limits when querying OpenRouter analytics data points?

Yes, OpenRouter analytics queries have specific time range limits for different data points based on available time granularities. Checking the schema reference ensures your query stays within valid limits and returns the expected results.

Can I analyze OpenRouter API spend and performance broken down by model and country?

Yes, you can analyze OpenRouter API spend and performance by model and country. The schema provides the necessary dimensions and metrics to break down cost, volume, and performance data according to your specific business requirements.