> ## Documentation Index > Fetch the complete documentation index at: https://docs.particle.pro/llms.txt > Use this file to discover all available pages before exploring further. # Find experts > Ranks the people listed under an occupation or field of research, most likely first, with their expertise as GET /v1/people/{id}/expertise describes it. Narrow by standing, seniority, whether they still practice the occupation, how they know their field, a second field, or their employer. Occupations and fields accept a code, slug, or title (browse them with GET /v1/people/occupations and GET /v1/people/fields). Hosts, guests, panelists, and correspondents are read once linked to a podcast appearance. ## OpenAPI ````yaml /openapi.json get /v1/people/expertise openapi: 3.1.0 info: contact: email: api@particle.pro name: Particle url: https://particle.pro description: >- Podcast API for transcripts, mentions and sponsorship data. 140,000+ podcasts transcribed, diarized and speaker-identified within minutes of airing, about 28,000 episodes a day. Search transcripts by keyword or meaning, track brand and company mentions with alerts, pull sponsor and ad-read data and rankings. REST API plus an MCP server for AI agents. Also company, people and topic intelligence. summary: >- Podcast API: transcripts, mentions, sponsors and rankings for 140,000+ podcasts. termsOfService: https://particle.pro/legal/tos-api title: Particle API version: 0.1.0 x-guidance: >- Podcast, people, company and topic intelligence. Authenticate with a pp_ API key (X-API-Key header) or pay per request with x402: a keyless call to a billable endpoint returns 402 with the payment requirements in the PAYMENT-REQUIRED header; sign the USDC transfer and repeat the request with PAYMENT-SIGNATURE. Start with GET /v1/podcasts/search?q=; the slugs in responses are the inputs to the other endpoints. Docs: https://docs.particle.pro; setup playbook: https://api.particle.pro/agents.md; endpoint and tool map with prices: https://api.particle.pro/llms.txt; credential recipe: https://api.particle.pro/auth.md. x-logo: url: https://particle.pro/favicon.svg servers: - url: https://api.particle.pro security: - ApiKeyHeader: [] - BearerAuth: [] externalDocs: url: https://docs.particle.pro paths: /v1/people/expertise: get: tags: - People - tier:standard summary: Find experts description: >- Ranks the people listed under an occupation or field of research, most likely first, with their expertise as GET /v1/people/{id}/expertise describes it. Narrow by standing, seniority, whether they still practice the occupation, how they know their field, a second field, or their employer. Occupations and fields accept a code, slug, or title (browse them with GET /v1/people/occupations and GET /v1/people/fields). Hosts, guests, panelists, and correspondents are read once linked to a podcast appearance. operationId: list-experts parameters: - description: >- Rank people listed under this occupation: a SOC 2018 or ISCO-08 code (29-1212), slug (cardiologists), or title (Cardiologists). Browse values with GET /v1/people/occupations. A name both standards share means the SOC occupation. Either occupation or field is required. explode: false in: query name: occupation schema: description: >- Rank people listed under this occupation: a SOC 2018 or ISCO-08 code (29-1212), slug (cardiologists), or title (Cardiologists). Browse values with GET /v1/people/occupations. A name both standards share means the SOC occupation. Either occupation or field is required. maxLength: 200 type: string - description: >- Keep people listed under this ANZSRC 2020 field of research: a code (320101), slug, or title. Browse values with GET /v1/people/fields. Without an occupation, people are ranked under the field. explode: false in: query name: field schema: description: >- Keep people listed under this ANZSRC 2020 field of research: a code (320101), slug, or title. Browse values with GET /v1/people/fields. Without an occupation, people are ranked under the field. maxLength: 200 type: string - description: >- Keep people whose standing is recognized this way (see standing on GET /v1/people/{id}/expertise). explode: false in: query name: standing schema: description: >- Keep people whose standing is recognized this way (see standing on GET /v1/people/{id}/expertise). enum: - established - self_described - unverified type: string - description: Keep people at this seniority or above. explode: false in: query name: seniority schema: description: Keep people at this seniority or above. enum: - professional - senior - distinguished type: string - description: >- Keep people who still work in the occupation, rather than having worked in it. Needs a detailed SOC 2018 occupation. explode: false in: query name: practicing schema: description: >- Keep people who still work in the occupation, rather than having worked in it. Needs a detailed SOC 2018 occupation. type: boolean - description: Keep people who know their field in this capacity. explode: false in: query name: capacity schema: description: Keep people who know their field in this capacity. enum: - researcher - licensed_professional - practitioner - executive_founder - public_official - journalist_analyst - creator_entertainer - athlete_coach - clergy - firsthand - layperson type: string - description: >- Keep people whose organization is this company: its slug (microsoft-corporation), domain (microsoft.com), or ID. explode: false in: query name: employer schema: description: >- Keep people whose organization is this company: its slug (microsoft-corporation), domain (microsoft.com), or ID. type: string - description: Results per page. explode: false in: query name: limit schema: default: 25 description: Results per page. format: int64 maximum: 100 minimum: 1 type: integer - description: Opaque cursor from the previous page. explode: false in: query name: cursor schema: description: Opaque cursor from the previous page. type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/PagePersonExpert' description: OK '402': content: application/problem+json: schema: $ref: '#/components/schemas/PlatformError' description: >- Payment Required. Read error_code. payment_required is the x402 path: either a keyless request being challenged — pay $0.03 in USDC per request (requirements in the PAYMENT-REQUIRED header) or send a pp_ API key — or a supplied payment that failed settlement (details in the PAYMENT-RESPONSE header; retry the same signature before signing a new one). See https://docs.particle.pro/x402. Any other code means the credential was accepted but does not cover this request (a plan or session gate such as premium_required or paid_plan_confirmation_required); its resolve says how to obtain access, and no payment header is sent. default: content: application/problem+json: schema: $ref: '#/components/schemas/PlatformError' description: Error x-codeSamples: - label: cURL lang: curl source: |- curl -H "X-API-Key: $PARTICLE_API_KEY" \ "https://api.particle.pro/v1/people/expertise?limit=25" components: schemas: PagePersonExpert: additionalProperties: false properties: cursor: description: Pass to next request for more results type: string data: description: List of results items: $ref: '#/components/schemas/PersonExpert' type: - array - 'null' has_more: description: Whether more results exist type: boolean required: - data - has_more type: object PlatformError: additionalProperties: false properties: detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string error_code: type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string resolve: $ref: '#/components/schemas/ErrorResolve' status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string type: object PersonExpert: additionalProperties: false properties: expertise: $ref: '#/components/schemas/PersonExpertise' description: >- What the person's records say about their expertise, as GET /v1/people/{id}/expertise returns it. person: $ref: '#/components/schemas/PersonCompact' description: The person. required: - person - expertise type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object ErrorResolve: additionalProperties: false properties: action: type: string endpoint: type: string message: type: string method: type: string url: type: string required: - message type: object PersonExpertise: additionalProperties: false properties: capacity: description: >- How the speaker knows their field: researcher, licensed_professional, practitioner, executive_founder, public_official, journalist_analyst, creator_entertainer, athlete_coach, clergy, firsthand, or layperson. Omitted when no single capacity is likely. type: string career_start_year: description: >- The year of the earliest dated role or degree in the speaker's records. format: int64 type: integer credential: description: >- A sentence from the speaker's records, verbatim, that states their credentials. type: string experience: description: >- How long the speaker's career spans, from the earliest dated role or degree in their records or as the records state it; omitted under ten years or when the records do not say. enum: - at_least_10_years - at_least_25_years type: string fields: description: >- The ANZSRC 2020 fields of research the speaker is listed under, most specific first (see GET /v1/people/fields). items: $ref: '#/components/schemas/ExpertiseCode' type: - array - 'null' occupations: description: >- The SOC 2018 occupations, then the ISCO-08 groups, the speaker is listed under, most specific first. Filter by any of them with its code, slug, or title (see GET /v1/people/occupations). items: $ref: '#/components/schemas/PersonOccupation' type: - array - 'null' organization: $ref: '#/components/schemas/PersonOrganization' description: Where the speaker works, when their records name an organization. seniority: description: >- The highest level the speaker has reached in their field; omitted below professional. enum: - professional - senior - distinguished type: string standing: description: >- How the speaker's standing is recognized: established (conferred by others: a credential, a position, recognition in the field), self_described (claimed by the speaker), or unverified (the records do not say, which never means the speaker is not an expert). enum: - established - self_described - unverified type: string required: - standing type: object PersonCompact: additionalProperties: false properties: description: description: Short description (e.g. current role), when known. type: string id: description: Encoded Person identifier type: string image_url: description: Canonical headshot URL when one is known for the Person type: string name: description: Display name type: string slug: description: >- Stable human-readable handle (e.g. 'satya-nadella'). Recommended canonical identifier on every Particle Pro person surface. type: string required: - id - name type: object ExpertiseCode: additionalProperties: false properties: code: description: >- The standard's own notation, such as 29-1212 (SOC), 2212 (ISCO), or 320101 (FoR). type: string level: description: >- Depth in the standard's official hierarchy: SOC major group 1 and detailed occupation 2; FoR division 1, group 2, field 3; ISCO-08 unit group 4 and minor group 3. ISCO-08 codes are the groups SOC maps to, listed flat without the standard's upper levels. format: int64 type: integer parent_code: description: >- Code one level up; omitted at the top level and for every ISCO-08 code, since ISCO-08 is listed without its upper levels. type: string slug: description: The title as a URL segment, such as cardiologists. type: string standard: description: >- The standard the code belongs to: soc_2018 (US Standard Occupational Classification), isco_08 (the ILO's International Standard Classification of Occupations), or anzsrc_for_2020 (ANZSRC Fields of Research). enum: - soc_2018 - isco_08 - anzsrc_for_2020 type: string title: description: The standard's official title, such as Cardiologists. type: string required: - standard - code - title - slug - level type: object PersonOccupation: additionalProperties: false properties: code: description: >- The standard's own notation, such as 29-1212 (SOC), 2212 (ISCO), or 320101 (FoR). type: string established: description: >- Whether others conferred the speaker's standing in this occupation, such as a licence or an appointment, rather than the speaker describing it. Present for detailed SOC 2018 occupations only. type: boolean level: description: >- Depth in the standard's official hierarchy: SOC major group 1 and detailed occupation 2; FoR division 1, group 2, field 3; ISCO-08 unit group 4 and minor group 3. ISCO-08 codes are the groups SOC maps to, listed flat without the standard's upper levels. format: int64 type: integer parent_code: description: >- Code one level up; omitted at the top level and for every ISCO-08 code, since ISCO-08 is listed without its upper levels. type: string practicing: description: >- Whether the speaker still works in this occupation, as opposed to having worked in it. Present for detailed SOC 2018 occupations only. type: boolean slug: description: The title as a URL segment, such as cardiologists. type: string standard: description: >- The standard the code belongs to: soc_2018 (US Standard Occupational Classification), isco_08 (the ILO's International Standard Classification of Occupations), or anzsrc_for_2020 (ANZSRC Fields of Research). enum: - soc_2018 - isco_08 - anzsrc_for_2020 type: string title: description: The standard's official title, such as Cardiologists. type: string required: - standard - code - title - slug - level type: object PersonOrganization: additionalProperties: false properties: company: $ref: '#/components/schemas/CompanyCompact' description: The company the organization is, when it is linked to one. kind: description: >- What kind of organization it is: university, research_institute, government, military, think_tank, financial_firm, company, media_outlet, own_company, nonprofit, religious_organization, or sports_team. type: string name: description: The organization's name as the speaker's records give it. type: string required: - name type: object CompanyCompact: additionalProperties: false properties: description: description: Short company description, when known. type: string domain: description: Primary website domain (e.g. 'nvidia.com'), when known. type: string id: description: Company identifier (domain, slug, or encoded ID) type: string image_url: description: Company logo or image URL type: string name: description: Company name type: string slug: description: >- Stable human-readable handle (the linked knowledge-graph slug, e.g. 'nvidia'), when known. Companies have no slug of their own; prefer this for display and pass it (or id) to /v1/companies. type: string ticker: description: Primary stock ticker symbol, when listed. type: string required: - id - name type: object securitySchemes: ApiKeyHeader: description: Pass your API key in the X-API-Key header (recommended). in: header name: X-API-Key type: apiKey BearerAuth: description: Pass your API key as a Bearer token in the Authorization header. scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.