Skip to content

docs(openrouter-analytics-schema): sync with openrouter-web changes #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devin-ai-integration wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(openrouter-analytics-schema): sync with openrouter-web changes #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions skills/openrouter-analytics-schema/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,20 +119,22 @@ 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

**Available with all time ranges:**
- `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

Expand Down