> For the complete documentation index, see [llms.txt](https://learn.mdjusticepassport.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mdjusticepassport.org/attorney-referrals/view-passport.md).
# View Passport
This article will show you how to view a potential client's Maryland Justice Passport.
***
The second step in the Attorney Referrals process is to view the potential client's Passport. If you have selected that you do not have a conflict of interest, you will be given read only access to the potential client's Passport.
#### How to view a potential client's Passport
1. A few moments after you select that you do not have a conflict of interest, a box will appear that provides the link to the potential client's Passport. Click on the link. You can also get to the potential client's Passport by going to the [Passports page](https://app.mdjusticepassport.org/mjp20/passports) and clicking on the potential client's name.
2. Once in the Passport, click through the tabs at the top of the page to review the information. You may need to wait a few moments and refresh the Passport to see all of the content, which takes a few moments to load after access is given.
{% hint style="info" %}
At this point in the process, the potential client's contact information will not be displayed.
{% 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://learn.mdjusticepassport.org/attorney-referrals/view-passport.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.