> For the complete documentation index, see [llms.txt](https://verify-doc.tiller-verify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verify-doc.tiller-verify.com/service-information/the-checks/proof-of-address-upload.md). # Proof of Address Upload The proof of residential address upload is designed to be used as a secondary form of proof for the individual’s current residential address of the user. This feature requires the user to send an image or PDF file of a selected qualifying document dated within the past three months. This individual can select from the following document types: * Telephone bill * Tax assessment notice * Water bill * Electricity or gas bill * Credit card statement This list is configurable. No electronic checks are performed against the document, it is simply uploaded as supplementary evidence. Users can view or download this document from the Verify Portal. It is also included within the individual’s PDF report if the POA is an image file. --- # 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://verify-doc.tiller-verify.com/service-information/the-checks/proof-of-address-upload.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.