> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/account-research/researching-an-account.md). # Researching an account Look up a company by domain to see its profile and inferred ICP. Account Research lets you look up any company by its domain and see a profile plus an inferred **ICP** (ideal customer profile) and ad-strategy read for that company. ## How it works 1. Enter a company's domain. 2. Primer shows a company card, then researches the company's ICP and ad strategy. 3. The ICP and ad analysis run in the background — Primer polls for up to about two minutes and shows **pending**, then **completed** (or **failed** if it couldn't finish). Researching a company is **read-only for your account**: it never changes your own organization's data or ICP. ## What the ICP tells you The ICP read includes a **market characterization** — a plain-language label describing how broad the company's market is (for example *narrow and high-intent*, *moderately broad*, or *broad and horizontal*). It's a descriptive summary, not a score. > Account Research is on-demand: you research a company when you ask. It does not send intent alerts or notifications on its own. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.sayprimer.com/primer/account-research/researching-an-account.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.