> For the complete documentation index, see [llms.txt](https://docs.dexscreener.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexscreener.com/contact-us/advertise.md).

# Advertise

If you're interested in advertising on DEX Screener we have the following option available.

### **Direct deal**

If you're in need of an advertising solution that requires customization to your exact needs:&#x20;

* Presales
* Ads on specific chains and/or specific pages
* Anything else&#x20;

**Pricing:** Fixed, minimum budget of $100,000 USD&#x20;

**Payment method:** Coinbase Commerce and Stripe&#x20;

KYC required

**Contact us directly:** ads (at) dexscreener.com

In order to advertise on our website, users and companies will have to pass the verification process, including KYC, to be able to launch their campaigns. *\*Please note that even if the process has been completed successfully, we and our partner reserve the right not to promote the project on the website.* \
&#x20;\
Note that a response may take up to 24 hours during a working day and up to 72 hours during holidays and weekends.&#x20;

Alternative communication meanings like Telegram are also available and will be confirmed by email (to prevent fake impersonators) from an official email address.


---

# 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.dexscreener.com/contact-us/advertise.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.
