> For the complete documentation index, see [llms.txt](https://docs.spicychat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spicychat.ai/product-guides/creating-chatbots/name.md).
# Name
The Name is a core part of your character’s identity. It’s how they will appear in chats and what other users will see if you choose to make the character public. Choose a name that aligns with the purpose, personality, and storyline of your character.
You can set the name of your character by navigating to the “Name” section of the creation screen. Character names don’t have to be unique, multiple characters can share the same name.
* Names should be between 3 to 20 characters long,
* You can use letters, numbers, spaces, dashes (-), and underscores (\_) in your character's name.
* You can opt for a single name ("John"), a full name ("John Doe"), or a unique handle ("The\_John").
A character’s name can strongly influence how your character behaves, especially if they lack a detailed personality. Names tied to well-known figures, like “Shakespeare,” may prompt the AI to adopt traits or speech patterns commonly associated with that individual. If you haven’t provided a lot of information, the name becomes a powerful cue, influencing how your character engages in conversation.
---
# 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.spicychat.ai/product-guides/creating-chatbots/name.md?ask=&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.
