> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/entity-types/entity-type-custom-model/model-entity-type-new.md).

# Starting a new model-based type

To start a new custom entity type:

1. On the **Additional Entity Types** page, click **Add Custom Entity Type.**
2. On the **Add Custom Entity Type** panel, click **Model-based**, then click **Next**.

<figure><img src="https://3072847115-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvOPn7KQptPWmS5iKg5P0%2Fuploads%2FFBhe5aUKXo1reTIrl7H4%2FCustomEntityType_AddPanel.png?alt=media&amp;token=01edeb41-b527-441f-87d8-6abfd415b5ac" alt=""><figcaption><p>Panel to select the type of custom entity type to create</p></figcaption></figure>

2. On the next panel, in the **Custom entity type name** field, provide a name for the custom entity type.
3. In the **Annotation guidelines** text area, provide instructions for how the model should identify values that you want to find. This is the first version of the model guidelines.

<figure><img src="https://3072847115-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvOPn7KQptPWmS5iKg5P0%2Fuploads%2Fdzmcgt3OCIk3EQnYNtOg%2FCustomEntityTypeModelBasedNew.png?alt=media&amp;token=57070927-3e9c-42a0-981e-a658d7b737d1" alt=""><figcaption><p>Panel to provide the name and initial guidelines for a model-based custom entity type</p></figcaption></figure>

4. Click **Next**.

Textual displays the **Test data setup** page.


---

# 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.tonic.ai/textual/entity-types/entity-type-custom-model/model-entity-type-new.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.
