> For the complete documentation index, see [llms.txt](https://docs.njpropertyrecords.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.njpropertyrecords.com/fundamentals/search.md).
# Search
Use the Search Page to quickly locate tax assessment, sales history, and foreclosure data for a specific property or block.
## Using the Search Bar
The Search Bar provides a quick and simple way to locate properties in our system.
1. Click the Search Bar and type all or a portion of: a property's address; a name; block & lot; or an APN/PIN. You can also conduct an advanced search. [Click here](/extras/glossary.md#advanced-search-criteria-definitions) for details.
2. Use the tabs on the left to specify what you're searching for.\
Any related results appear below the Search Bar.
3. Click on a result to open the related Property Page.
{% hint style="info" %}
When you initiate a search from the Street Map Page, the platform remains on the Street Map and displays the location of the searched property. When you initiate a search on any other page, clicking a desired property takes you to the Property Page, where all available information about the searched property is displayed.
{% endhint %}
## Using the Search Page
The Search Page offers more advanced search functionality compared to the Search Bar.
To open the Search Page, click **Search** from the navigation panel.
---
# 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.njpropertyrecords.com/fundamentals/search.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.
