metaculus.com APImetaculus.com ↗
Access Metaculus prediction questions, community forecasts, resolution status, and question details via a structured API. Two endpoints, paginated results.
curl -X GET 'https://api.parse.bot/scraper/54188bf5-5799-4d5a-b7cb-e1e69c3939eb/get_pending_resolution_questions?limit=5&offset=0' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch questions with pending resolution status from Metaculus. Returns paginated results with question metadata, forecaster counts, topics, subquestions, and community predictions.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of questions per page. |
| offset | integer | Pagination offset. Use next_offset from a previous response to fetch the next page. |
{
"type": "object",
"fields": {
"has_more": "boolean, whether more pages exist",
"questions": "array of question objects with id, title, slug, url, status, topics, categories, nr_forecasters, question_type, and subquestions",
"next_offset": "integer or null, offset for next page",
"total_on_page": "integer, number of questions returned on this page",
"previous_offset": "integer or null, offset for previous page"
},
"sample": {
"data": {
"has_more": true,
"questions": [
{
"id": 30333,
"url": "https://www.metaculus.com/questions/30333/will-any-frontier-lab-have-its-model-weights-stolen-before-january-1-2030/",
"slug": "will-any-frontier-lab-have-its-model-weights-stolen-before-january-1-2030",
"title": "Will the model weights of any AI system developed by a frontier AI lab be stolen or leaked before January 1, 2030?",
"status": "open",
"topics": [],
"resolved": false,
"categories": [
"Artificial Intelligence"
],
"created_at": "2024-11-20T15:29:58.496579Z",
"short_title": "Will any frontier lab have its model weights stolen before January 1, 2030?",
"published_at": "2024-11-22T18:31:00.045401Z",
"subquestions": [
{
"id": 30132,
"type": "binary",
"label": "Your forecast",
"title": "Will the model weights of any AI system developed by a frontier AI lab be stolen or leaked before January 1, 2030? (Your forecast)",
"status": "open",
"resolution": null,
"scheduled_close_time": "2029-12-31T12:00:00Z",
"scheduled_resolve_time": "2031-01-01T12:00:00Z"
}
],
"comment_count": 0,
"question_type": "group",
"nr_forecasters": 8,
"author_username": "skmmcj",
"group_description": "...",
"actual_resolve_time": null,
"resolution_criteria": "...",
"scheduled_close_time": "2029-12-31T12:00:00Z",
"scheduled_resolve_time": "2031-01-01T12:00:00Z"
}
],
"next_offset": 5,
"total_on_page": 5,
"previous_offset": null
},
"status": "success"
}
}About the metaculus.com API
The Metaculus API gives developers access to forecasting questions and prediction data from Metaculus.com across 2 endpoints. Use get_pending_resolution_questions to retrieve paginated lists of questions awaiting resolution — including forecaster counts, topics, categories, and subquestions — and get_question_detail to pull full metadata on any individual question, including resolution criteria, community vote score, and fine print.
Endpoints Overview
The API exposes two endpoints. get_pending_resolution_questions returns a paginated list of Metaculus questions that are pending resolution. Each page yields an array of question objects with fields including id, title, slug, url, status, topics, categories, nr_forecasters, question_type, and any associated subquestions. Pagination is controlled via limit and offset parameters; use next_offset from a response to walk through subsequent pages, and check has_more to determine whether additional results exist.
Question Detail
get_question_detail accepts a question_id (the numeric Metaculus post ID) and returns a richer object for that single question. Response fields include title, status, resolved (boolean), topics, categories, fine_print, vote_score, and the full url and slug. This is the endpoint to use when you need resolution criteria or the community vote score for a specific question.
Data Shape and Coverage
The pending resolution endpoint is scoped to questions in a pending-resolution state; it does not return the full Metaculus question catalog. The subquestions field on list results lets you identify conditional or group questions without fetching each detail record individually. nr_forecasters gives the count of forecasters who have made predictions on a question, useful for filtering by prediction activity.
- Track all Metaculus questions currently pending resolution to monitor imminent outcome decisions.
- Filter prediction questions by topic or category using the
topicsandcategoriesfields. - Display forecaster participation counts (
nr_forecasters) to surface the most-predicted questions. - Retrieve full resolution criteria and fine print for any question via
get_question_detail. - Identify group or conditional questions by inspecting the
subquestionsfield on list results. - Sort or rank questions by community
vote_scoreto highlight highest-engagement forecasts. - Build a resolution alert system by polling pending questions and detecting
resolvedstatus changes.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Metaculus have an official developer API?+
What does `get_pending_resolution_questions` return, and how does pagination work?+
questions field, each with metadata such as id, title, status, topics, categories, nr_forecasters, question_type, and subquestions. Use the limit parameter to set page size and pass next_offset from the previous response as the offset parameter for the next page. The has_more boolean tells you whether further pages exist.Does the API return community prediction distributions or probability values for questions?+
nr_forecasters) and vote scores (vote_score), but do not expose numerical probability distributions or individual forecast values. The API covers pending-resolution question metadata and single-question detail records. You can fork it on Parse and revise to add an endpoint that returns community prediction aggregates for a given question ID.Is the full Metaculus question catalog available, or only pending-resolution questions?+
get_pending_resolution_questions is scoped to questions in a pending-resolution state. Open, resolved, and archived questions are not covered by the list endpoint. You can fork this API on Parse and revise it to add endpoints that query other question states.What is the `fine_print` field returned by `get_question_detail`?+
fine_print contains supplementary resolution details that are separate from the main resolution criteria — typically edge cases, ambiguity rules, or additional conditions the question author specifies. It is returned as a plain string and may be empty for questions that have none.