include: people for current leadership and notable people, products for the three-level product hierarchy, competitors for the competitor list. For sponsor/advertising analytics on this company, use particle_company_get_podcast_ad_presence instead.
Inputs
Output
A markdown document with the company name as an H2, identifier KV lines (**Slug:**, **Ticker:**, **Domain:**, **CIK:**, **QID:**, **Entity slug:** — only those that have values, and deduplicated: **Slug:** is omitted when it would repeat the Domain or ID rows, and **Entity slug:** when it would repeat **Slug:**. As the chaining handle, use **Slug:** when present, otherwise **Domain:** — both are accepted by company_slug parameters; a ticker is not, so when neither row is present re-resolve via particle_company_resolve with the ticker), then a paragraph with the description. The following H3 sections appear when the matching include value was requested and data is present:
### People— one bullet per person, formattedName (slug) — title. The parenthesized slug feedsparticle_person_get.### Products— an indented bullet hierarchy- **Name** (level, status)(segment → product_line → product).### Competitors— one bullet per competitor:- Name (handles) — competitive_basis.
company_slug="nvidia", include=["people","products","competitors"], truncated):
Example
Related
- REST equivalent:
GET /v1/companies/{id}, with sub-resources for people, products, and competitors. - For sponsor analytics, use
particle_company_get_podcast_ad_presence. - For dialogue mentioning the company, use
particle_podcast_find_mentionswithcompany_slug.