Skip to main content
GET
/
datasets
/
app-rankings
Top apps by token usage
curl --request GET \
  --url https://openrouter.ai/api/v1/datasets/app-rankings \
  --header 'Authorization: Bearer <token>'
{
  "data": [
    {
      "app_id": 12345,
      "app_name": "Cline",
      "rank": 1,
      "total_requests": 4321,
      "total_tokens": "12345678"
    },
    {
      "app_id": 67890,
      "app_name": "Roo Code",
      "rank": 2,
      "total_requests": 2109,
      "total_tokens": "9876543"
    }
  ],
  "meta": {
    "as_of": "2026-05-12T02:00:00Z",
    "end_date": "2026-05-11",
    "start_date": "2026-04-12",
    "version": "v1"
  }
}

Authorizations

Authorization
string
header
required

API key as bearer token in Authorization header

Query Parameters

category
enum<string>

Marketplace category group to filter by (e.g. coding). Only apps tagged with a subcategory inside this group are returned. Mutually combinable with subcategory — when both are supplied the subcategory must belong to the category group.

Available options:
coding,
creative,
productivity,
entertainment
Example:

"coding"

subcategory
enum<string>

Marketplace subcategory to filter by (e.g. cli-agent). Takes precedence over category for the actual filter; when category is also supplied the pair must be consistent.

Available options:
cli-agent,
ide-extension,
cloud-agent,
programming-app,
native-app-builder,
creative-writing,
video-gen,
image-gen,
audio-gen,
roleplay,
game,
writing-assistant,
general-chat,
personal-agent,
legal
Example:

"cli-agent"

sort
enum<string>
default:popular

popular ranks apps by total token volume inside the date window. trending ranks apps by absolute excess token growth: window volume minus the average volume of the three equal-length periods immediately preceding the window. Apps with no excess growth are omitted from trending results.

Available options:
popular,
trending
Example:

"popular"

start_date
string

Start of the date window in YYYY-MM-DD (UTC), inclusive. Defaults to 30 days before end_date. The dataset begins at 2025-01-01; earlier values are clamped forward to that floor and the resolved value is echoed in meta.start_date.

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2026-04-12"

end_date
string

End of the date window in YYYY-MM-DD (UTC), inclusive. Defaults to the most recent completed UTC day. Must be on or after 2025-01-01; earlier values are rejected with a 400.

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2026-05-11"

limit
integer
default:50

Maximum number of apps to return (1-100). Defaults to 50.

Required range: 1 <= x <= 100
Example:

50

offset
integer | null
default:0

Number of ranked apps to skip before the first returned row (0-100). Defaults to 0. rank stays absolute, so the first row of offset=50 is rank: 51.

Required range: 0 <= x <= 100
Example:

0

Response

Apps ranked per the requested sort, re-numbered 1..N. popular sorts by total_tokens descending; trending sorts by absolute excess token growth descending and may return fewer than limit rows.

data
object[]
required

Apps ranked per the requested sort, re-numbered 1..N after category filtering. popular sorts by total_tokens descending; trending sorts by absolute excess token growth descending and may return fewer than limit rows when few apps are growing.

meta
object
required
Example:
{
  "as_of": "2026-05-12T02:00:00Z",
  "end_date": "2026-05-11",
  "start_date": "2026-04-12",
  "version": "v1"
}