> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Kernel.ai: Kernel Get Combined

> Get the status and result of a company match-and-enrich job, given its job ID. Includes SDK V2 examples, input constraints, response fields, and Deepline cost.

Get the status and result of a company match-and-enrich job, given its job ID.

> [!NOTE]
>
> Tool ID: `kernel_get_combined`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'kernel_get_combined',
  {
    "job_id": "job_123"
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute kernel_get_combined --input '{
  "job_id": "job_123"
}' --json
```

## Example response

The SDK returns this shape at `result.toolResponse.raw`. The example values illustrate the response.

```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
{
  "data": {
    "status": "pending"
  }
}
```

Use `deepline describe kernel_get_combined --json` for the latest machine-readable contract.

## Input reference

Returns the status and result of a combined job. When `status` is `completed`, the `record` object contains the entity resolution result and the requested enrichment.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.job_id` | `string` | Yes | — | Job ID returned by the POST endpoint |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Returns the status and result of a combined job. When `status` is `completed`, the `record` object contains the entity resolution result and the requested enrichment.",
    "properties": {
      "job_id": {
        "type": "string",
        "description": "Job ID returned by the POST endpoint"
      }
    },
    "required": [
      "job_id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `object` | Yes | — | Provider response payload. |
| `result.data.id` | `string` | No | — | Unique identifier for the job. Present when `status` is `pending`, `processing`, or `completed`. |
| `result.data.jobid` | `string` | No | — | Unique identifier for the job. Present only when `status` is `failed`. |
| `result.data.status` | `"pending" \| "processing" \| "completed" \| "failed"` | Yes | — | Current status of the job. Terminal states are `completed` and `failed`. Allowed: `pending`, `processing`, `completed`, `failed`. |
| `result.data.created_at` | `string` | No | — | ISO 8601 timestamp when the job was created. Format: `date-time`. |
| `result.data.completed_at` | `string` | No | — | ISO 8601 timestamp when the job reached a terminal state. Format: `date-time`. |
| `result.data.subprocesses` | `object` | No | — | Status of each requested subprocess while a combined job is running. Added locally because Kernel's official processing\_with\_subprocesses example documents this response field but CombinedJobStatus omits it. |
| `result.data.subprocesses.entity-resolution` | `"pending" \| "processing" \| "completed" \| "failed"` | No | — | Allowed: `pending`, `processing`, `completed`, `failed`. |
| `result.data.subprocesses.resolve-parent` | `"pending" \| "processing" \| "completed" \| "failed"` | No | — | Allowed: `pending`, `processing`, `completed`, `failed`. |
| `result.data.subprocesses.firmographics` | `"pending" \| "processing" \| "completed" \| "failed"` | No | — | Allowed: `pending`, `processing`, `completed`, `failed`. |
| `result.data.record` | `object` | No | — | — |
| `result.data.record.kernel_id` | `string \| null` | Yes | — | The unique identifier for the resolved entity in Kernel's database. `null` when no entity is resolved. |
| `result.data.record.identity_type` | `"legal_entity" \| "trading_entity"` | No | — | Type of identity resolved. Allowed: `legal_entity`, `trading_entity`. |
| `result.data.record.identity_resolution_confidence` | `"HIGH" \| "MEDIUM" \| "LOW"` | Yes | — | Confidence that the resolved identity is correct. Allowed: `HIGH`, `MEDIUM`, `LOW`. |
| `result.data.record.identity_resolution_reasoning` | `string` | Yes | — | Explanation of how the identity was resolved. |
| `result.data.record.legal_info` | `object \| null` | Yes | — | Legal entity information. `null` when no entity is resolved. |
| `result.data.record.legal_info.country` | `string \| null` | Yes | — | Country of the legal entity. |
| `result.data.record.legal_info.reasoning` | `string` | Yes | — | Explanation of how the legal entity was identified. |
| `result.data.record.legal_info.trading_name` | `string \| null` | Yes | — | Trading name associated with the legal entity. |
| `result.data.record.legal_info.confidence` | `"HIGH" \| "MEDIUM" \| "LOW"` | Yes | — | Confidence in the legal entity info. Allowed: `HIGH`, `MEDIUM`, `LOW`. |
| `result.data.record.legal_info.legal_name` | `string \| null` | Yes | — | Registered legal name. |
| `result.data.record.legal_info.website` | `string \| null` | Yes | — | Official URL of the legal entity. |
| `result.data.record.trading_info` | `object \| null` | Yes | — | Trading entity information. `null` when no entity is resolved. |
| `result.data.record.trading_info.country` | `string \| null` | Yes | — | Country of the trading entity's operational region. |
| `result.data.record.trading_info.website` | `string \| null` | Yes | — | Primary trading website URL. |
| `result.data.record.trading_info.reasoning` | `string` | Yes | — | Explanation of how the trading identity was identified. |
| `result.data.record.trading_info.trading_name` | `string \| null` | Yes | — | Primary trading name. |
| `result.data.record.trading_info.confidence` | `"HIGH" \| "MEDIUM" \| "LOW"` | Yes | — | Confidence in the trading identity info. Allowed: `HIGH`, `MEDIUM`, `LOW`. |
| `result.data.record.entity_classification` | `object \| null` | Yes | — | Classification of the entity. `null` when no entity is resolved. |
| `result.data.record.entity_classification.type` | `string` | Yes | — | Entity category. One of: Company, Government, Education. |
| `result.data.record.entity_classification.subtype` | `string` | Yes | — | Entity sub-category. E.g. Operating, HoldCo/Investment, Business Unit, Establishment. |
| `result.data.record.entity_classification.reasoning` | `string \| null` | No | — | Explanation of the classification. |
| `result.data.record.linkedin` | `object \| null` | No | — | LinkedIn profile match. Only present when `match_to_linkedin` is true. |
| `result.data.record.linkedin.url` | `string \| null` | No | — | Full LinkedIn company profile URL. |
| `result.data.record.linkedin.slug` | `string \| null` | No | — | Company slug extracted from the LinkedIn URL. |
| `result.data.record.linkedin.match_type` | `"actual" \| "indicative" \| "none"` | No | — | How the LinkedIn profile was matched. `actual` is a verified direct match. `indicative` is a best-guess match. `none` when no match was found. Allowed: `actual`, `indicative`, `none`. |
| `result.data.record.linkedin.reasoning` | `string \| null` | No | — | Explanation of how the LinkedIn match was determined. |
| `result.data.record.firmographics` | `object` | No | — | — |
| `result.data.record.firmographics.kernel_id` | `string` | Yes | — | The unique identifier for the entity in Kernel's database. |
| `result.data.record.firmographics.op_status` | `object \| null` | Yes | — | Operational status of the entity. `null` when not yet determined. |
| `result.data.record.firmographics.op_status.operational_status` | `"Active" \| "Out of business" \| "Absorbed" \| "Undetermined" \| null` | No | — | Current operational status. Allowed: `Active`, `Out of business`, `Absorbed`, `Undetermined`, `null`. |
| `result.data.record.firmographics.op_status.reasoning` | `string \| null` | No | — | Explanation of how the operational status was determined. |
| `result.data.record.firmographics.location` | `object \| null` | Yes | — | Operating and registered addresses. `null` when not yet determined. |
| `result.data.record.firmographics.location.operating` | `object \| null` | No | — | Operating address. |
| `result.data.record.firmographics.location.operating.street` | `string \| null` | No | — | Street address. |
| `result.data.record.firmographics.location.operating.city` | `string \| null` | No | — | City. |
| `result.data.record.firmographics.location.operating.state` | `string \| null` | No | — | State or province. |
| `result.data.record.firmographics.location.operating.country` | `string \| null` | No | — | Country. |
| `result.data.record.firmographics.location.operating.postcode` | `string \| null` | No | — | ZIP or postal code. |
| `result.data.record.firmographics.location.operating.reasoning` | `string \| null` | No | — | Explanation of how the address was determined. |

The table shows the first 50 fields. Use the live contract below for every field.

> [!NOTE]
>
> This output schema is too large for an inline display. Read the complete live contract with `deepline describe kernel_get_combined --json`.

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Kernel.ai provider guide](https://deepline.com/docs/providers/kernel/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.