> For the complete documentation index, see [llms.txt](https://docs.ndi.video/all/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ndi.video/all/faq/ndi-certified/what-happens-if-my-product-doesnt-meet-the-requirements-for-certification.md).

# What happens if my product doesn’t meet the requirements for Certification?​

Our goal is to work with you before you ship your product for testing to ensure your efforts aren’t wasted. By submitting your proposed certified product information, we can work with you to get it to the point for us to test and approve. In the unfortunate event that it doesn’t meet the requirements, we will make an effort to continue working with you to get your product approved. If we can’t, we will let you know that further development and design is needed and provide you with specific directions on where to improve your product. The intent is to preload all the requirements and technical information up front so Certification is more of a final check than a first step.


---

# 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.ndi.video/all/faq/ndi-certified/what-happens-if-my-product-doesnt-meet-the-requirements-for-certification.md?ask=<question>&goal=<user_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.
