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

# DT Exchange Demand

DT Exchange Demand is a portal that allows you to integrate as an RTB Bidder and participate in real-time bidding for ad inventory.

For more information, see the [DT Exchange](https://www.digitalturbine.com/dt-exchange) product page and contact DT to confirm your eligibility.

## Technical Specifications <a href="#h_01jqkbks5g46tjwc4w3x7exzt6" id="h_01jqkbks5g46tjwc4w3x7exzt6"></a>

* Data Center Location: The DT data center is in Virginia (US-East in AWS).
* Timeout: 350ms for responding with an ad.
* OpenRTB Version: DT supports [OpenRTB API Specification Version 2.5](https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf). For more information, see [DT Exchange OpenRTB 2.5 Specs](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs).
* Impression Counting: DT counts display impressions when at least one pixel is visible to the user. Video impressions are calculated according to the standard VAST protocol.


---

# 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.digitalturbine.com/dt-ads-demand/dt-exchange-demand.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.
