Subfield Peer Topics API: One topic in, its OpenAlex subfield peers out with works volume, 3y
One topic in, its OpenAlex subfield peers out with works volume, 3y growth and momentum rank from our weekly scan, term-matched peers first. Honest about subfield breadth via term_matched. 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/related — product id
science_related. Over MCP, call answerpool_get with
product_id=science_related.
curl "https://answerpool.io/v1/science/related?q=quantum+computing"
Live call: https://answerpool.io/v1/science/related?q=quantum+computing · JSON sample: /v1/samples/science_related
What does the answer look like?
A representative response, the same static sample served at /v1/samples/science_related.
as_of | 2026-09-03T14:00:00Z |
|---|---|
data_as_of | 2026-08-30 |
anchor_topic_id | T10320 |
anchor_name | Quantum Computing Algorithms and Architecture |
grouped_by | subfield |
group_value | Computational Theory and Mathematics |
count | 1 |
term_matched | 1 |
note | Peers share the anchor's OpenAlex subfield (or field if the subfield is unknown), ordered by shared terms with the anchor then by momentum rank. OpenAlex subfi… |
disclaimer | Derived from OpenAlex (CC0) by AnswerPool's weekly scan; not investment advice. |
refresh_after | 2026-09-18T00:00:00.000Z |
topics
| topic_id | name | works_last_full_year | growth_3y | momentum_rank | is_emerging |
|---|---|---|---|---|---|
| T11216 | Quantum Error Correction | 812 | 0.44 | 61 | true |
The same sample as raw JSON
{
"as_of": "2026-09-03T14:00:00Z",
"data_as_of": "2026-08-30",
"anchor_topic_id": "T10320",
"anchor_name": "Quantum Computing Algorithms and Architecture",
"grouped_by": "subfield",
"group_value": "Computational Theory and Mathematics",
"count": 1,
"term_matched": 1,
"topics": [
{
"topic_id": "T11216",
"name": "Quantum Error Correction",
"works_last_full_year": 812,
"growth_3y": 0.44,
"momentum_rank": 61,
"is_emerging": true
}
],
"note": "Peers share the anchor's OpenAlex subfield (or field if the subfield is unknown), ordered by shared terms with the anchor then by momentum rank. OpenAlex subfields are broad, so `term_matched` says how many peers share wording with the anchor \u2014 when it is 0 these are subfield neighbours, not close topical matches.",
"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.
- OpenAlex (CC0) — upstream:
https://api.openalex.org
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 have a topic and want its subfield peers ranked, for landscape mapping.
What you skip building
- OpenAlex subfield traversal
- guessing adjacent topic names
When should you not use it?
A graded verdict on one topic — /v1/technology/momentum ($0.05, LLM-graded).
Where else can you find this?
- Catalog entry (JSON, free)
- OpenAPI schema — input and output types, prices, the 402 flow
- llms.txt — every product in one plain-text document