---
title: "List Companies"
method: GET
path: "/internal/evals/requirement-applicability/companies"
tags: ["internal"]
---

# List Companies

`GET /internal/evals/requirement-applicability/companies`

## Request

- Base URL: `https://api.kobaltlabs.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.kobaltlabs.com/internal/evals/requirement-applicability/companies`
- Auth: none declared

Companies a comparison could be run for, by name.

Offered on either of two grounds, and the option carries both so the surface can tell them apart:
a company with a decomposed **library**, or one with marketing standards **attached to a live
product line**. The second used to be excluded on the argument that a company without a library
has nothing to narrow — true, but it made the dashboard unreachable for exactly the companies it
is meant to be pointed at, because a library has to be built through this surface before it
exists. `/preparation` builds it, so having something to decompose is now a reason to be listed.

Kobalt Labs' own company is excluded by default, the way every other internal drill-down
excludes it, but `include_kobalt` opts it back in — unlike those drill-downs this one is not
reporting on customers, and Kobalt's tenant is where a library gets seeded to try the dashboard
at all. `start_run` never had the exclusion, so the picker matches what the API already accepted.

## Query parameters

- `include_kobalt` boolean

## Response `200`

Successful Response

- CompanyOption[]
  - `company_id` string, uuid, required
  - `company_name` string, required
  - `guidelines_with_library` integer, required
  - `guidelines_attached` integer, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/kobaltlabs/apis/kobaltlabs-api.md) - [All operations](https://skmtc.dev/kobaltlabs/apis/kobaltlabs-api/llms.txt) - [OpenAPI document](https://skmtc.dev/kobaltlabs/apis/kobaltlabs-api/revisions/8587332d5e43?raw)