AnswerPool

Science Field Map API: Every research field with tracked-topic count, recent works volume — OpenAlex

Every research field with tracked-topic count, recent works volume, emerging-topic count and its top-momentum topic — the one-call landscape map. Free, no key.

Free — no key, no signup, rate-limited to 60 calls per minute per client.

How do you call it?

GET /v1/science/fields — product id science_fields. Over MCP, call answerpool_get with product_id=science_fields.

curl "https://answerpool.io/v1/science/fields"

Live call: https://answerpool.io/v1/science/fields · JSON sample: /v1/samples/science_fields

What does the answer look like?

A representative response, the same static sample served at /v1/samples/science_fields.

as_of2026-09-03T02:00:00Z
count1
disclaimerDerived from OpenAlex (CC0) by AnswerPool's weekly scan; not investment advice.
refresh_after2026-09-18T00:00:00.000Z

fields

fieldtopicsworks_last_full_yearemerging_topicstop_topic
Computer Science31251204441Large Language Model Agents
The same sample as raw JSON
{
 "as_of": "2026-09-03T02:00:00Z",
 "count": 1,
 "fields": [
  {
   "field": "Computer Science",
   "topics": 312,
   "works_last_full_year": 512044,
   "emerging_topics": 41,
   "top_topic": "Large Language Model Agents"
  }
 ],
 "disclaimer": "Derived from OpenAlex (CC0) by AnswerPool's weekly scan; not investment advice.",
 "refresh_after": "2026-09-18T00:00:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change daily, so every response carries a refresh_after timestamp — right now it would be 2026-09-18T00:00:00.000Z. Schedule the next call on that value rather than on a guess.

Method version 0.1.0 · serving cache 7 days · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

You want the field-level map before topic-level analysis.

What you skip building

When should you not use it?

Topic-level detail — use /v1/science/topics.

Where else can you find this?