> For the complete documentation index, see [llms.txt](https://docs.ayetstudios.com/v/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ayetstudios.com/v/product-docs/faq/declined-placements.md).
# Declined Placements
We decline placements for several reasons. Some of the reasons are listed below:
* You didn't set up the placement correctly
* Your app / website failed to reach our quality criteria
* We reached out to you with additional questions, but you didn't get back to us
* You set up an API / Network placement for which only selected publishers are eligible
\
You couldn't find a reason for which we might have declined your placement?
No problem, getting declined isn't the end of the world. We are happy to discuss why we declined your placement in detail. Hopefully, there is a chance to work out a solution together.
{% hint style="info" %}
In order to find out more, please reach out via email at:
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ayetstudios.com/v/product-docs/faq/declined-placements.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.