/metaculus/users

POST /api/metaculus/users

Price: 20 credits

Get a Metaculus forecaster profile with their track record

How to use it

Get a Metaculus forecaster by username, id or profile URL with their track record: average score, per-question scores over time, score histogram and calibration curve, plus forecast and comment counts. Use users/questions and users/comments for their authored content.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Metaculus username, user id or profile URL (examples: "NMorrison", "130973", "https://www.metaculus.com/accounts/profile/130973/"; minLength: 1)

Response

• @type string (default: "MetaculusUser")
• id string required
• alias string required
• url string nullable
• image string nullable
• bio string nullable
• occupation string nullable
• location string nullable
• website_url string nullable
• formerly_known_as string nullable
• twitter string nullable
• linkedin string nullable
• facebook string nullable
• github string nullable
• good_judgement_open string nullable
• kalshi string nullable
• manifold string nullable
• infer string nullable
• hypermind string nullable
• is_active boolean nullable
• is_bot boolean nullable
• is_spam boolean nullable
• is_pro boolean nullable
• joined_at integer nullable
• average_score number nullable
• forecast_count integer nullable
• questions_predicted_count integer nullable
• score_count integer nullable
• posts_authored_count integer nullable
• notebooks_authored_count integer nullable
• forecasts_on_authored_questions_count integer nullable
• comment_count integer nullable
• score_history array (default: [])
  • @type string (default: "MetaculusScorePoint")
  • post_id string nullable
  • question string nullable
  • resolution string nullable
  • score number nullable
  • scored_at integer nullable
• score_histogram array (default: [])
  • @type string (default: "MetaculusScoreBin")
  • bin_start number nullable
  • bin_end number nullable
  • score_count integer nullable
• calibration_curve array (default: [])
  • @type string (default: "MetaculusCalibrationBin")
  • bin_lower number nullable
  • bin_upper number nullable
  • average_resolution number nullable
  • lower_confidence_interval number nullable
  • upper_confidence_interval number nullable
  • perfect_calibration number 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 — User not found 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.