> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/types-of-custom-field/radio-list.md).

# Radio List

<figure><img src="/files/OsuJnDUQGXgk4KeMUqxr" alt=""><figcaption></figcaption></figure>

The radio list field type allows you to create a series of options, only one of which can be selected.

This can be used to create multiple-choice questions for a user. The value field is used to set the actual value attached to the item, whilst the text field functions as only the text that will be displayed. This means that the value field is mandatory; otherwise, the system will see the option as being blank despite anything entered in the text field.

The value field can also be populated with different text from that in the text field, allowing you to have both substantial information for reports and a friendly user interface.

{% hint style="warning" %}
Do not duplicate any value fields, as this will prevent the system from functioning properly.
{% endhint %}


---

# 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.agilecase.com/administrator-documentation/types-of-custom-field/radio-list.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.
