> For the complete documentation index, see [llms.txt](https://dmtp.gitbook.io/dmtp-sdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmtp.gitbook.io/dmtp-sdk/readme.md).

# 1. Introduction to Apps Network

## What is Web3 Traffic Exchange?

At no cost, Web3 Traffic Exchange (Apps Network) is a decentralized platform where projects get and spend tokens to exchange user traffic. Developers showcase their games to acquire tokens, then use these tokens to promote their own projects across the network. This fosters mutual growth in the Web3 ecosystem, allowing developers to increase their user base.

The core concept is simple yet powerful: by displaying ads for other projects on your site, you earn points. These points can then be used to have your own ads displayed across the network of participating web3 properties. This creates a self-sustaining ecosystem where everyone contributes to and benefits from increased visibility within the web3 community.

![Web3 Traffic Exchange System Diagram](/files/TgBYKlmEKkJZ7KZgkC3m)

## Benefits for Web3 Projects

Participating in the Web3 Traffic Exchange offers several key advantages:

1. **Targeted Exposure**: Reach an audience already interested in web3 games.
2. **Cost-Effective Growth**: Earn advertising credits by promoting others, eliminating the need for large marketing budgets.
3. **Community Building**: Connect with other web3 games, fostering collaborations and partnerships.
4. **Offer Wall Ad Formats**: Offer wall is a full-page interstitials featuring web3 games.

In the following sections, we'll guide you through the process of getting started, creating ad campaigns, managing your inventory, and maximizing the benefits of this unique traffic exchange system.


---

# 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://dmtp.gitbook.io/dmtp-sdk/readme.md?ask=<question>&goal=<endgoal>
```

`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.