> For the complete documentation index, see [llms.txt](https://api.veratad.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.veratad.com/knowledge-base/best-practices.md). # Best Practices ## What data should I send with each request? You must send the required fields and if you use an additional matching ruleset you must provide that element or the transaction will fail. That said, when searching for an individual in the data sources it is always more helpful to provide as much data as you collect. The more information we have on a person, the more people we will find. ## Does Veratad store the input request? No, Veratad does not store any sensitive PII information from your request. The only exception to this rule is when you use the document storage service. ## How should I use the reference field? Since Veratad does not store sensitive PII it is important for you to send a unique value in the reference field with each request. This will help for reporting and audit trail purposes. --- # 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://api.veratad.com/knowledge-base/best-practices.md?ask=&goal= ``` `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.