> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/data-types/text.md). # Text ### Description A text is a sequence of characters like a string, a word or a sentence, most commonly used to store text inputs and for labels. The text literal can consist of zero or more characters enclosed by double quotes. The Text datatype can include all alphanumeric characters and symbols available in the Unicode Standard: * letters * numbers * symbols * whitespace-characters (spaces, newlines, tabs) Even though text can contain numbers it will be treated as text. When a text is used, only the characters between the quotes are shown - when you need to display the double-quotes, you need to use the escape character directly in front of it: `\"`. ### Formatting Special characters are escaped with a backslash (`\`). ### Unknown An unknown value can be written as `UnknownText`. ### Examples ``` "Hello World!" "Greetings Mr Doe." "" "The wolf said: \"Little pig, little fatty, let me come in.\"." ``` --- # 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.wem.io/platform/wemreference/data-types/text.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.