Skip to main content
Associate requests with Identity identifiers for user-level observability and analytics.
Identities are Orq.ai entities used to track project expenses and token usage per user or team.

Why use identity tracking

  • Per-user cost attribution and cross-charging to tenants or customers.
  • Enforcing per-user rate limits to prevent abuse.
  • Identifying which users generate the most load or cost.
  • Linking LLM usage to existing user analytics for cohort analysis.

Use Cases

Quick Start

Pass a stable identifier from the system (a database user ID, UUID, or similar string) as identity.id on any request.

Identity resolution

The gateway checks each of the following sources in order and uses the first match found:
Pass the identity object in the request body to attribute the request and keep the identity record up to date. See the Quick Start above for full examples.

Configuration

Identities: manage, list, and view metrics

Covers creating identities via the dashboard or API, listing with 30-day usage metrics, and retrieving identity records.