/lmarena/leaderboards

POST /api/lmarena/leaderboards

Price: 1 credit

Get an LMArena leaderboard by arena and category

How to use it

Elo from human blind votes, so this is preference rather than a benchmark score, and the confidence interval matters: two models whose `rating_lower`/`rating_upper` overlap are not separated by the data even though their `rank` differs. `vote_cutoff_at` is the snapshot date, which trails today by days. Per-language and exclude-ties boards are categories here, not separate filters, and each arena accepts only its own categories.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• arena string required — Arena whose leaderboard to return (one of: "code", "document", "image-edit", "image-to-code", "image-to-video", "search", "text", "text-to-image", "text-to-video", "video-to-video", "vision")
• category string nullable — Category board inside the arena; omitted returns the overall board (one of: "3d-modeling", "art", "brand-marketing", "captioning", "cartoon", "chat", "chinese", "code", "coding", "commercial-design", "consumer-product", "content-creation-tools", "creative-writing", "data-analytics", "diagram", "english", "entity-recognition", "exclude-ties", "expert", "french", "frontend", "fullstack", "gaming", "german", "hard-prompts", "hard-prompts-english", "homework", "html", "humor", "industry-business-and-management-and-financial-operations", "industry-entertainment-and-sports-and-media", "industry-legal-and-government", "industry-life-and-physical-and-social-science", "industry-mathematical", "industry-medicine-and-healthcare", "industry-software-and-it-services", "industry-writing-and-literature-and-language", "instruction-following", "japanese", "korean", "longer-query", "math", "multi-image-edit", "multi-image-edit-3d-modeling", "multi-image-edit-art", "multi-image-edit-cartoon", "multi-image-edit-commercial-design", "multi-image-edit-photorealistic", "multi-image-edit-portraits", "multi-image-edit-text-rendering", "multi-turn", "non-english", "ocr", "overall", "photorealistic", "polish", "portraits", "react", "reference-based-design", "russian", "simulations", "spanish", "text-rendering", "work")
• count integer required — Max result count (min: 1)

Response

• @type string (default: "LmarenaLeaderboardEntry")
• id string required
• arena string required
• category string required
• model_key string required
• model_name string nullable
• model_url string nullable
• organization string nullable
• license string nullable
• release_type string nullable
• rank integer nullable
• rank_upper integer nullable
• rank_lower integer nullable
• rating number nullable
• rating_upper number nullable
• rating_lower number nullable
• vote_count integer nullable
• context_length integer nullable
• input_price_per_million number nullable
• output_price_per_million number nullable
• price_per_image number nullable
• price_per_second number nullable
• is_style_controlled boolean nullable
• vote_cutoff_at string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No leaderboard for that arena and category Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.