Skip to main content
Companies in Particle API map across every identifier system you might already have. Look up Nvidia by ticker, by domain, by SEC CIK, or by knowledge-graph slug — you’ll always land on the same record. From there you can pull a structured product hierarchy, follow the company’s appearances across podcasts, fetch its competitors, or pull sponsor analytics for its ad presence.
Available to MCP agents as particle_company_resolve and particle_company_get.

Identifiers

Every company carries a single identifiers block: Use any of them as a query filter on list-companies. The slug, domain, and canonical ID resolve directly in the {id} slot of singular endpoints; for ticker, CIK, or QID, query GET /v1/companies?ticker=… (or ?cik=… / ?qid=…) first and pass the returned slug, domain, or ID through the singular endpoint.

List companies

Response

Filter parameters

Fetch many at once

When you already hold a set of company slugs, domains, or IDs — the same identifiers /v1/companies/{id} accepts — pass them as a comma-separated ids list to fetch them all in a single request instead of one call per company, up to 100 per call. Companies come back in the same shape 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 identifiers against what you sent to find any that are missing.
Unlike entity_id (which filters companies by their linked knowledge-graph entity), ids is a direct multi-get of companies by their own identifier. When ids is present the other filters and pagination are ignored.

Get a single company

nvidia (slug), nvidia.com (domain), and 3CensCwu5G2oKCFgPrNf89 (canonical ID) all resolve directly via /v1/companies/{id} to the same response. To look up a company by NVDA (ticker), 0001045810 (CIK), or Q182477 (QID), call GET /v1/companies with the matching query filter (?ticker=NVDA, ?cik=…, ?qid=…) and use the returned slug, domain, or canonical ID with the singular endpoint.

Sub-resources

See Products for the product hierarchy and Advertising for the sponsor analytics shape.

Cross-referencing with the knowledge graph

The entity_slug field on every company doubles as a knowledge-graph handle. Use it to find every podcast appearance, mention, and clip where the company is discussed:
The company_id filter on the episodes and mentions endpoints accepts a slug, domain, or canonical ID — the same handles that resolve directly via /v1/companies/{id}.