Alphaxiv Find Researchers

1 credits/call
ae_alphaxiv_find_researchers

Find researchers by research topic or name, current organization or role, citation range, position history, and verified coauthorship. Use this tool first for organization rosters, who has left an organization, career moves, and what researchers are doing now. Results include researcher handles in the form [SLUG=...]. Supply your search criteria in request_body. For subject searches, prefer topic and describe one focused concept using the terminology of papers in that field. Use affiliation and role for current positions, or position for historical roles and dates; all conditions within position apply to the same LinkedIn experience entry. Combine current and historical filters to investigate transitions. Use page and limit to browse further matches. For collaborator, advising, or lab-membership questions, set relationship.kind to coauthored_with and provide the anchor researcher's full name or exact [SLUG=...] handle in relationship.researcher. Relationship results summarize evidence from linked public alphaXiv papers: shared publications, their share of each candidate's output, lead-author counts on papers where the anchor is last author, collaboration years, and current position. Use require_position_overlap with position.affiliation to narrow candidates to people with overlapping time at that organization. If the anchor has no dated position there, the results report that limitation and rely on coauthorship. These records help assess possible relationships; an exact advising or lab title needs a source that explicitly states it. Do not use this tool only to resolve a name for another profile or relationship call; pass the name directly to that call.

AcademicSearch
1 credits/call

Pricing

1 credits/call
ConditionCharge
Each call1 credits/call

Parameters

Optional parameters use the platform defaults when omitted.

ParameterTypeRequiredDescriptionDefault
pageintegerNo1-based page over the same ordering. Every result says whether more matched beyond it, so page on when the answer needs the tail rather than re-running a narrower search. A page that reports no total is not a count of the roster; only the last page of a search establishes one.1
rolestringNoCurrent role to filter by, token-matched ('professor' matches assistant and associate professors; 'phd student'). Only current roles are indexed. Omit or leave empty when not filtering by role.—
sortenum (relevance | citations | recent_activity | relationship_strength)No'relevance' ranks a query, or relationship strength for a relationship-only search, otherwise citations. 'recent_activity' ranks by latest linked paper. 'relationship_strength' requires relationship.relevance
limitintegerNoResults per page. Defaults to 12, or 50 for a relationship search, whose rows are one line each.—
querystringNoA person's name only when identifying that person is the final task, or a research subject ('mechanistic interpretability'). Never use this to resolve an anchor for another call; pass the name directly there. Omit for structured roster, relationship, or career queries.—
topicstringNoResearch subject to answer from authorship of papers on it, for 'who works on X' and 'who does prominent work on X'. One concept in the vocabulary its own papers use — name the architecture, benchmark, or subfield, and spell out an acronym alongside it. Never concatenate several related concepts to widen the net: that lands between all of them and matches none, and 'generalist robotic policies evaluation benchmarking robot foundation models embodied AI' returned none of the field's benchmark authors where 'evaluating and benchmarking generalist robotic policies' returned four in the top five. Prefer this over `query` for any subject question, since `query` matches profile prose and far fewer researchers describe their work there than publish it.—
positionobjectNoComposable LinkedIn position-history filter. Affiliation, role, status, and every date bound apply to the same experience row. For a recent departure use a past position with ended_after and end-date ordering; combine with top-level affiliation or role for transitions.—
position.rolestringNoTitle or role for this position, token-matched against the same experience row.—
position.statusenum (current | past | any)NoWhether the matching position is ongoing, ended, or either.any
position.order_byenum (start_date | end_date)NoOrder matching positions newest-first by their start or end date.—
position.affiliationstringNoOrganization for this position, matched against the same experience row under every indexed spelling.—
position.ended_afterstringNoPosition ended on or after this date, inclusive (YYYY-MM-DD).—
position.ended_beforestringNoPosition ended on or before this date, inclusive (YYYY-MM-DD).—
position.started_afterstringNoPosition began on or after this date, inclusive (YYYY-MM-DD).—
position.started_beforestringNoPosition began on or before this date, inclusive (YYYY-MM-DD).—
position.exclude_current_matchesarrayNoHistorical dimensions that must no longer match a current position. For who-left-X use ['affiliation']; include 'role' only when the title must also have changed.[]
affiliationstringNoCurrent organization ('DeepSeek', 'UC Berkeley'). Every indexed spelling of it is matched, so write the name plainly and never spell out variants yourself. For a historical organization use position.affiliation, or include_past_affiliations as shorthand.—
relationshipobjectNoCoauthorship evidence from linked public alphaXiv papers, one line per coauthor: shared papers, what share of that person's own output the collaboration is, how often they lead a paper the anchor closes, the years it ran, and their current position. Judge each row yourself — a senior collaborator and a student both share many papers, and only the share and lead counts tell them apart. require_position_overlap composes it with position history to add shared time; an exact title comes from a source that states one.—
relationship.kindstringYesNo parameter description.—
relationship.researcherstringYesThe anchor researcher's full name or exact raw [SLUG=...] handle.—
relationship.min_shared_papersintegerNoOptional shared-paper floor. Omit for roster discovery, which defaults to 1; set it only when the user asks for frequent or close collaborators.—
relationship.require_position_overlapbooleanNoWhen true, the candidate's matching position must overlap a dated position the anchor held at position.affiliation, using indexed year/month precision. Narrows student and lab-member candidates to shared time; if the anchor has no dated position there, the results say so and stand on coauthorship.—
max_citationsintegerNoCitation ceiling, e.g. to find rising researchers who are not yet famous.—
min_citationsintegerNoCitation floor, to keep a roster to established researchers.—
topic_authorsenum (lead | senior | any)NoWhich byline slot `topic` weights: 'lead' for the students and postdocs who drive the work, 'senior' for the PIs who close the author list, 'any' for both.lead
include_past_affiliationsbooleanNoShorthand for a past position at `affiliation`, excluding researchers whose current affiliation still matches. Use `position` for role or date constraints.false

Invocation example

Parameter template

Generated from the parameter configuration. Replace the sample values before use.

POST/agent-api/v1/tool/executeX-Api-Key
Request coderequest.sh
curl --request POST \
  --url 'https://agentearth.ai/agent-api/v1/tool/execute?tool_name=ae_alphaxiv_find_researchers' \
  --header "X-Api-Key: $AGENTEARTH_API_KEY" \
  --header 'Content-Type: application/json' \
  --data-raw '{
  "params": {}
}'

No response example available yet.