> 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/data/foundational-data/location.md). # Location {% embed url="" %} Location sounds like one field. In Kernel, it is deliberately two: where the entity operates, and where it is legally registered. The operating address is where the entity actually works. Think headquarters, head office, main office, or the physical site your CRM account is meant to track. The registered address is the legal address from a corporate registry or another authoritative filing. For most companies, these addresses are the same. Kernel mirrors them unless the evidence says there is a real split. ## How Kernel determines location Kernel researches location from company websites, regulatory filings, news reports, business registrations, and other evidence tied to the resolved entity. The split matters in common cases. A company may be registered at an agent address but operate from another city. A branch, store, plant, or office may operate at one street address while the legal entity is registered somewhere else. A remote-first company may have no operating street address but still have a registered office. Use operating location for territory assignment, routing, and understanding where work actually happens. Use registered location for legal identity, compliance, and incorporation context. ## Fields | Field | Description | | ------------------------------- | ----------------------------------------------------------------- | | `location.operating` | Primary operating address for the resolved entity. | | `location.operating.street` | Street address, when supported by evidence. | | `location.operating.city` | City for the operating address. | | `location.operating.state` | State, province, or region for the operating address. | | `location.operating.country` | Country for the operating address. | | `location.operating.postcode` | Postal code for the operating address. | | `location.operating.reasoning` | Explanation of how the operating address was determined. | | `location.registered` | Registered or legal address for the resolved entity. | | `location.registered.street` | Street address from the registry or legal source, when available. | | `location.registered.city` | City for the registered address. | | `location.registered.state` | State, province, or region for the registered address. | | `location.registered.country` | Country for the registered address. | | `location.registered.postcode` | Postal code for the registered address. | | `location.registered.reasoning` | Explanation of how the registered address was determined. | The useful part is not just having two addresses. It is knowing which question each address answers. --- # 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: ``` GET https://docs.kernel.ai/data/foundational-data/location.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.