> For the complete documentation index, see [llms.txt](https://docs.tradingpost.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradingpost.finance/general-information/trading-post-intro.md).

# Trading Post Intro

Welcome to Trading Post!

Trading Post is a native social-first DEX built on Camp. Trading Post is the home for the teams and tokens built on Camp to provide them with a venue to trade their tokens. Allowing both users and the builders to leverage our trading venue for the best trading experience. Liquidity provider tools are also essential for Trading Post and allow for better yield capture for LPs.

## Why Camp?

Camp Network is the user identity layer across blockchains. Camp aggregates online user data, enabling users to own and monetize their identity while helping teams like us Trading Post better understand user behavior. 

This allows us to bring in social aspects to the trading experience that had previously been an isolated experience. 

{% embed url="<https://docs.campnetwork.xyz/>" %}


---

# 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.tradingpost.finance/general-information/trading-post-intro.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.