> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/speech-recognition-voice-input/introduction-and-prerequisites.md).
# Introduction and Prerequisites
When using the LogicNets Assessment Framework you have the ability to enable end-users of your application to use voice controls to answer questions and to navigate through the assessments. This allows end-users to complete an assessment without looking at the screen and to answer assessment questions without using a keyboard or mouse.
LogicNets has worked closely with [G2Speech](https://www.g2speech.com/) to integrate software that improves voice-recognition results and provides specialized medical, legal, and technical dictionaries.
Before you can use speech integration in your LogicNets-based application, you need the following prerequisites:
* LogicNets speech license for the speech package
* G2Speech setup (G2Cursor + RSDK + license)
* Optionally, a microphone with appropriate voice-recognition drivers. (Note: You can use any recording device, but LogicNets advises using a high-quality dictation microphone for optimal recognition results; for example, the Philips Speech Mike III is well tested and used for speech with LogicNets.
Please contact LogicNets' Sales Support for further details: .
---
# 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://community-test.logicnets.com/release-9/platform-documentation/advanced-topics/speech-recognition-voice-input/introduction-and-prerequisites.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.