> For the complete documentation index, see [llms.txt](https://docs.entangle.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.entangle.fi/universal-token-standard/developer-guides/manual-deploy/token-deployment-types.md).

# Token Deployment Types

UTS offers three distinct types of token deployments for manually deployed tokens, each with its own characteristics.

## Custom Tokens

* Can be launched by anyone
* Not officially registered on the Entangle platform
* Token and connector contracts can be modified by deployers as needed
* Offer maximum flexibility but may lack official recognition

## Factory Tokens

* Deployed through Factory contracts
* In the case of UTS Connectors deployment:
  * Underlying tokens remain owned by third parties
  * Provides a standardized deployment process
* Offers a balance between customization and standardization

## Verified Tokens

* Registered and vetted by Entangle
* Official recognition on the Entangle platform
* Increased trust and credibility for token projects

For more detailed information about how to verify your token on Entangle platform please visit [GitHub](https://github.com/Entangle-Protocol/UTS-Public-Token-List) or check out the [token verification](/universal-token-standard/developer-guides/token-verification.md) guide.


---

# 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://docs.entangle.fi/universal-token-standard/developer-guides/manual-deploy/token-deployment-types.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.