> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/overview/readme.md).

# Introduction

{% embed url="<https://pub-8e1d08f439ec43bdbb79f1055a273a02.r2.dev/kernel-introduction-kernel-ai-4a4ca76a.mp4>" %}

Territory planning, account coverage, and revenue operations all depend on one thing: knowing exactly which entities are in your market, how they relate to each other, and whether your CRM reflects that accurately. Kernel makes that possible.

<figure><img src="/files/J0LVCZiM6v60Hy4qJwU3" alt="" width="563"><figcaption><p>Most Account records have one or more data quality issues</p></figcaption></figure>

### What Kernel is

Kernel is an entity database for RevOps teams. It gives every legal entity, subsidiary, and operating unit a universal KERN ID, then uses automated research to continuously maintain accuracy across your CRM.

#### What that means in practice:

1. Hierarchies that reflect how your team actually sells, not just legal filings
2. Duplicates resolved and parent-child relationships corrected at scale
3. Custom attributes like verticals, team sizes, and technographics, without manual research
4. Every change is risk-scored, auditable, and applied on your terms

#### Why Kernel is different:

Most third-party data vendors share the same limitations: generic data, stale hierarchies, and limited ability to customize to how you sell.

Kernel combines a proprietary entity database, research workflows, and native data management. The database provides the structural foundation others lack. Kernel then applies that foundation across your entire CRM, continuously, without manual correction cycles.

<figure><img src="/files/uqlcdg4bCv8cLlAAdzKB" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kernel.ai/overview/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
