> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/database-validation/person-search-verification.md). # Person Search Verification *** ### Overview Person search verification corroborates the identity attributes a user provides - such as **name, address, and date of birth** - against **aggregated identity records** drawn from public and commercial data sources. Rather than checking a single document against a single issuer, it looks for consistent evidence that the claimed identity exists and is associated with the details provided. #### What Gets Checked A person search typically evaluates whether the submitted attributes are **corroborated** across one or more record sources. Common signals include: * Whether the **name and address** appear together in established records * Whether the **date of birth** is consistent with those records * Whether the combination of attributes resolves to a **single, coherent identity** rather than conflicting or non-existent records The check returns a corroboration outcome - for example, a match, a partial match, or no match - that can be used on its own or combined with other database checks to raise assurance. #### What It Does and Doesn't Tell You * **It confirms** that the claimed identity is corroborated by independent records and is consistent across sources. * **It does not authenticate** the person in real time, and it is not a sanctions, watchlist, or credit screen - pair it with the appropriate dedicated checks where those are required. * **Coverage and data depth vary** by region and by the attributes supplied. Sparser records may return a partial or inconclusive result for legitimate users. {% hint style="info" %} Person search is best used as a **corroborating** signal alongside document and biometric verification, not as a standalone proof of identity. {% endhint %} --- # 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://docs.1kosmos.com/identity-verification/database-validation/person-search-verification.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.