/metaculus/leaderboards

POST /api/metaculus/leaderboards

Price: 20 credits

Get a Metaculus leaderboard for a period or a tournament

How to use it

Get Metaculus leaderboard standings: the global peer, baseline, comment-insight or question-writing leaderboard for a period starting in a given year, or the standings of one tournament. Bot and aggregate entries appear beside people.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of entries to return (examples: 50; min: 1)
• score_type string — Global leaderboard to return (default: "peer_global"; one of: "peer_global", "baseline_global", "comment_insight", "question_writing", "peer_global_legacy")
• year integer nullable — First year of the period, the current year when omitted (examples: 2025)
• duration integer — Length of the period in years (default: 1; examples: 1, 2; min: 1; max: 10)
• tournament string nullable — Metaculus tournament alias, id or URL for its standings (examples: "aibq3"; minLength: 1)

Response

• @type string (default: "MetaculusLeaderboardEntry")
• id string required
• rank integer nullable
• user object nullable
  • @type string (default: "MetaculusUserRef")
  • id string required
  • alias string nullable
  • url string nullable
  • is_bot boolean nullable
  • is_staff boolean nullable
  • is_pro boolean nullable
• aggregation_method string nullable
• score number nullable
• ci_lower number nullable
• ci_upper number nullable
• coverage number nullable
• contribution_count integer nullable
• medal string nullable
• prize number nullable
• percent_prize number nullable
• take number nullable
• is_excluded boolean nullable
• show_when_excluded boolean nullable
• exclusion_status string nullable
• leaderboard_id string nullable
• leaderboard_name string nullable
• score_type string nullable
• project_id string nullable
• period_start_at integer nullable
• period_end_at integer nullable
• is_finalized boolean nullable
• calculated_at integer 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 period or tournament 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.