From f52a72689a193a17005f6fff413329d02edffef8 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Sat, 18 Jul 2026 17:04:55 +0000 Subject: [PATCH] docs(openrouter-analytics-schema): sync with openrouter-web changes Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- skills/openrouter-analytics-schema/SKILL.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/skills/openrouter-analytics-schema/SKILL.md b/skills/openrouter-analytics-schema/SKILL.md index d05608b..70e8b94 100644 --- a/skills/openrouter-analytics-schema/SKILL.md +++ b/skills/openrouter-analytics-schema/SKILL.md @@ -119,12 +119,14 @@ Some dimensions have their raw IDs automatically resolved to human-readable labe |---|---| | `api_key_id` | Key name/label | | `app` | App title or origin URL | -| `user` | User name or email address | +| `user` | Two fields per row: `user` (name) + `user_email` (email) — see note below | | `workspace` | Workspace name | All other dimensions (e.g., `model`, `provider`, `country`) are returned as-is without resolution. -> Rows with an empty `user` value represent traffic not attributed to a specific org member (e.g., API keys created at the org level). +> **The `user` dimension is the exception.** Grouping by `user` returns **two** fields per row instead of one: `user` is the account's display name (`null` when the user has no name set), and `user_email` is their email (`null` when the user has no email on file). The raw Clerk user ID is never returned — use `user_email` to cross-reference users against your own records. + +> Rows where both `user` and `user_email` are `null` represent traffic not attributed to a specific org member (e.g., API keys created at the org level). ### Dimension Categories @@ -132,7 +134,7 @@ All other dimensions (e.g., `model`, `provider`, `country`) are returned as-is w - `model` — the OpenRouter model ID (permaslug) - `variant` — model variant (e.g., standard, extended) - `api_key_id` — which API key made the request -- `user` — the creator user ID (for org-level queries) +- `user` — org member breakdown (returns a `user` name field + a `user_email` field; see Label Resolution) - `workspace` — workspace ID - `app` — application ID