> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/support/faq/no-ams-support.md). # I seem to have found a problem with your software, but I am not subscribed to the AMS? Can you still provide me with support? We are always interested in improving our products, so we encourage you to submit a support request any time you find an issue. We will look into the issue based on a first-come, first-served basis, with AMS customers having priority. Our support team will email you with our findings as soon as the issue was identified and/or resolved. If the issue is reproduced and fixed in a new version of the software, you would need to purchase the AMS for your license(s) in order to get access to that version. If you do not have AMS, and have a general question, please feel free to post a question to one of our forums or on [StackOverflow](https://stackoverflow.com/questions/tagged/pdftron+or+pdfnet) using the `apryse` tag, and someone from the community can assist you. --- # 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.apryse.com/support/faq/no-ams-support.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.