# Intoduction

### [#](#where-should-i-start) Where should I start? <a href="#where-should-i-start" id="where-should-i-start"></a>

If you are brand new to Patex, we recommend checking out the guideline [For Developers](/tech/for-developers.md)[ ](https://patex.gitbook.io/test-patex-docs/for-developers/contracts-deployment)It'll get you familiar with the core steps required to work with a network. Luckily, Patex is EVM equivalent, so it's 100% the same as deploying a contract to Ethereum.

If you're a bit more familiar with Patex and Ethereum, you can try walking through one of the various [tutorials (opens new window)](https://github.com/patex-ecosystem/patex-tutorial) put together by the Patex community. They'll help you get a started when building your first Patex project.

### [#](#guides) Guides <a href="#guides" id="guides"></a>

These guides provide integration guidelines for specific topics. They are intended as one stop shops, and should have all the relevant information you need for completing a specific type of integration, from network information and tutorials to tips and tricks.

We're aiming to maintain guides for many of the common interactions that developers might have with Patex. For example, we have guides for adding Patex support to a [wallet](https://patex.gitbook.io/test-patex-docs/for-developers/add-to-wallet) or a [CEX](https://patex.gitbook.io/test-patex-docs/c-patex-centralized-patex). We also have guides for getting your [token onto the standard bridge (opens new window)](https://github.com/patex-ecosystem/patex-tutorial/tree/main/standard-bridge-standard-token).

Take a look at the list on the left for a complete list of the guides we've created so far.


---

# Agent Instructions: 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:

```
GET https://docs.patex.io/tech/patex-network/intoduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.