> ## 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.

# Companies

> Cross-referenced company profiles with SEC, Wikidata, ticker, domain, and knowledge-graph identifiers.

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.

<Note>Available to MCP agents as [`particle_company_resolve`](/mcp/tools/companies/company-resolve) and [`particle_company_get`](/mcp/tools/companies/company-get).</Note>

## Identifiers

Every company carries a single `identifiers` block:

| Identifier                  | Source                 | Example      |
| --------------------------- | ---------------------- | ------------ |
| `ticker`                    | Primary stock ticker   | `NVDA`       |
| `cik`                       | SEC Central Index Key  | `0001045810` |
| `qid`                       | Wikidata QID           | `Q182477`    |
| `domain`                    | Company domain         | `nvidia.com` |
| `entity_id` / `entity_slug` | Knowledge-graph entity | `nvidia`     |

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

<CodeGroup>
  ```bash curl theme={"dark"}
  curl "https://api.particle.pro/v1/companies?ticker=NVDA&limit=1" \
    -H "X-API-Key: $PARTICLE_API_KEY"
  ```

  ```js JavaScript theme={"dark"}
  const res = await fetch(
    "https://api.particle.pro/v1/companies?ticker=NVDA&limit=1",
    { headers: { "X-API-Key": process.env.PARTICLE_API_KEY } },
  );
  const { data } = await res.json();
  ```

  ```python Python theme={"dark"}
  res = httpx.get(
      "https://api.particle.pro/v1/companies",
      params={"ticker": "NVDA", "limit": 1},
      headers={"X-API-Key": os.environ["PARTICLE_API_KEY"]},
  )
  data = res.json()["data"]
  ```
</CodeGroup>

```json Response theme={"dark"}
{
  "data": [
    {
      "id": "3CensCwu5G2oKCFgPrNf89",
      "name": "Nvidia",
      "description": "Nvidia is a leading developer of graphics processing units…",
      "updated_at": "2026-02-15T08:41:32Z",
      "identifiers": {
        "cik": "0001045810",
        "qid": "Q182477",
        "entity_id": "nvidia",
        "entity_slug": "nvidia",
        "ticker": "NVDA",
        "domain": "nvidia.com"
      }
    }
  ],
  "has_more": false
}
```

### Filter parameters

| Parameter       | Description                                                                           | Example                               |
| --------------- | ------------------------------------------------------------------------------------- | ------------------------------------- |
| `q`             | Case-insensitive name search                                                          | `?q=Apple`                            |
| `ticker`        | Stock ticker(s), comma-separated, up to 100                                           | `?ticker=AAPL,GOOG`                   |
| `domain`        | Domain(s), comma-separated, up to 100                                                 | `?domain=apple.com,nvidia.com`        |
| `cik`           | SEC CIK(s), comma-separated, up to 100                                                | `?cik=0000320193,0001045810`          |
| `qid`           | Wikidata QID(s), comma-separated, up to 100                                           | `?qid=Q312,Q182477`                   |
| `entity_id`     | Knowledge-graph slug(s) or ID(s), comma-separated, up to 100                          | `?entity_id=apple,nvidia`             |
| `ids`           | Bulk multi-get by company slug, domain, or ID, comma-separated, up to 100 (see below) | `?ids=apple,tesla.com,nvidia`         |
| `updated_after` | Incremental sync filter                                                               | `?updated_after=2026-04-01T00:00:00Z` |

```bash theme={"dark"}
# Bulk lookup by tickers
curl "https://api.particle.pro/v1/companies?ticker=AAPL,NVDA,MSFT" \
  -H "X-API-Key: $PARTICLE_API_KEY"

# Incremental sync
curl "https://api.particle.pro/v1/companies?updated_after=2026-04-01T00:00:00Z" \
  -H "X-API-Key: $PARTICLE_API_KEY"
```

### 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.

```bash theme={"dark"}
curl "https://api.particle.pro/v1/companies?ids=apple,tesla.com,3CensCwu5G2oKCFgPrNf89" \
  -H "X-API-Key: $PARTICLE_API_KEY"
```

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

```bash theme={"dark"}
curl "https://api.particle.pro/v1/companies/nvidia" \
  -H "X-API-Key: $PARTICLE_API_KEY"
```

`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

| Endpoint                                     | Returns                                             |
| -------------------------------------------- | --------------------------------------------------- |
| `GET /v1/companies/{id}/products`            | Three-level product hierarchy with lifecycle status |
| `GET /v1/companies/{id}/competitors`         | Competitor list                                     |
| `GET /v1/companies/{id}/podcast/advertising` | Sponsor analytics for the company's ad presence     |

See [Products](/companies/products) for the product hierarchy and [Advertising](/podcasts/advertising#per-company-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:

```bash theme={"dark"}
# Episodes featuring or mentioning Nvidia
curl "https://api.particle.pro/v1/podcasts/episodes?company_id=nvidia&limit=5" \
  -H "X-API-Key: $PARTICLE_API_KEY"

# Every line of dialogue mentioning Nvidia, grouped by episode
curl "https://api.particle.pro/v1/podcasts/mentions?company_id=nvidia&limit=5" \
  -H "X-API-Key: $PARTICLE_API_KEY"
```

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}`.

## Related

* [Products](/companies/products) — recursive product tree with lifecycle status
* [Podcast advertising](/podcasts/advertising) — `/companies/{id}/podcast/advertising` and the leaderboard
* [Knowledge graph → entities](/knowledge-graph/entities) — follow a company across audio content