> For the complete documentation index, see [llms.txt](https://docs.motar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motar.com/motar-core-services/intro-to-core-services/admin/lists.md).

# Lists

**Click** on the "Lists" tab found on the left side of the admin application to see

* Hardware
* API Keys

### Hardware

The hardware type can be configured to what you would like your apps to be able to use on their distribution. Any visible options on this list will be selectable to the user when creating a distribution. 

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

**Clicking** "Add Hardware" at the bottom of the screen will open up the new hardware category modal

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

Fill in the hardware name and upload a thumbnail. **Click** "Add" and your new hardware category will show at the bottom of the existing list. You must add a subelement under the category.

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

**Click** the "Add Sub Element" button to and fill out the information for a subelement and then **click** "Add".

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

Your new sub element will be added

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

### API Keys

An **API key** (Application Programming Interface key) is a unique code used to identify and authenticate an application or developer when it makes a request to an API. It functions like a digital ID badge or a secret token, ensuring that only authorized programs can access the API's services

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

**Click** "+ New Key" to generate a new key at the bottom of the list.

API keys can be made active or inactive using the toggle.


---

# 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.motar.com/motar-core-services/intro-to-core-services/admin/lists.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.