slug (e.g. sam-altman, nvidia, kara-swisher) and a canonical id. Either is accepted anywhere an entity reference is needed.
Available to MCP agents as
particle_entity_resolve (the union resolver) and particle_person_resolve (people only).Search entities
Response (truncated)
Filter parameters
| Parameter | Description |
|---|---|
q | Name search (case-insensitive) |
type | Restrict to an entity category (e.g. person, company); see GET /v1/entities/types for the slugs |
podcast_id | Restrict to entities appearing in a specific podcast |
ids | Bulk multi-get: fetch a known set of entities by slug or ID in one call (see below) |
Get a single entity
Response
Fetch many at once
When you already hold a set of entity slugs or IDs, pass them as a comma-separatedids list to fetch them all in a single request instead of one call per entity — up to 100 per call. Entities come back in the same shape as search and in the order you asked for them. A ref that doesn’t resolve is simply left out (no error, no placeholder), so compare the returned slug/id values against what you sent to find any that are missing.
Response (truncated)
ids is present the other filters (q, type, podcast_id) and pagination are ignored — it is a direct multi-get of exactly the refs you supply.
Podcast appearances
To find every podcast episode where an entity has been featured or discussed across the catalog, uselist-episodes with an entity_id filter. Add a role filter to narrow to guest, host, panelist, correspondent, or mention.
Response (truncated)
role=guest to limit results to episodes where the entity was actually a guest, rather than every episode that happens to mention them.
A typical cross-referencing flow
The Quickstart walks the full flow end-to-end.
Related
- Topics — taxonomy companion to entities
- Companies → Overview — entities linked to company records
- Transcripts → Mentions — dialogue around entity mentions
- Concepts → IDs and slugs — slug resolution rules