particle_person_resolve.
The default response is lean. Request optional sections via include: external_links for LinkedIn/Wikipedia/social profiles, podcast_appearances for their most recent podcast appearances (episode and podcast slugs included for follow-up calls), companies for the full role history (the current role is included and marked (current)).
For podcast-guest analytics (appearance stats, suitability exposure, co-appearance graph) use particle_podcast_get_guest with the same slug.
Inputs
Output
A markdown document with the person’s name as an H2, then a**Slug:** row (or **ID:** when no slug is backfilled), a **Current role:** row (Title, Company), a **Entity slug:** row when it differs from the slug, and a bio paragraph. The following H3 sections appear when the matching include value was requested and data is present:
### Companies— one bullet per role, formattedCompany — Title (current)(the(current)marker appears on the active role).### External links— one bullet per platform, formattedPlatform: <url>(orPlatform: <identifier>for handle-only platforms).### Recent podcast appearances— one bullet per appearance, formattedEpisode title (episode-slug) on Podcast title (podcast-slug) — YYYY-MM-DD. The slugs round-trip into the podcast tools. (Capped at the 10 most recent; for the full paginated history useparticle_podcast_get_guestwithinclude: ["appearances"].)
person_slug="sam-altman", include=["companies","podcast_appearances"], truncated):
Example
Related
- REST equivalent:
GET /v1/people/{id}(request/response contract in the API reference). - For appearance analytics (stats, suitability exposure), use
particle_podcast_get_guestwith the same slug. - Resolve a name to a slug first with
particle_person_resolveorparticle_entity_resolve.