---
title: "Get Labels"
method: GET
path: "/agent/custom/label/list"
---

# Get Labels

`GET /agent/custom/label/list`

## Request

- Base URL: `https://api.tellers.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tellers.ai/agent/custom/label/list`
- Auth: none declared

The label vocabulary.

Readable by any signed-in user, unlike the routes that write it: an author
cannot pick from a list they are not allowed to see. Two segments rather
than ``/labels`` so it can never be mistaken for an assistant id by the
``/{custom_agent_id}`` routes.

## Query parameters

- `set_by` 'OWNER' | 'REVIEWER': Who may *attach* a label to an assistant. Creating one is reviewer-only either way: the vocabulary is curated, and an owner picks from it rather than inventing an entry — which is the whole reason nothing here has to screen what a label is called. OWNER says an author may put this label on their own assistant; REVIEWER reserves it, which is what keeps a ``featured`` from being self-awarded.

## Headers

- `x-api-key` string, nullable
- `authorization` string, nullable

## Response `200`

Successful Response

- APILabel[]
  - `id` string, required
  - `display_name` string, required
  - `set_by` 'OWNER' | 'REVIEWER', required: Who may *attach* a label to an assistant. Creating one is reviewer-only either way: the vocabulary is curated, and an owner picks from it rather than inventing an entry — which is the whole reason nothing here has to screen what a label is called. OWNER says an author may put this label on their own assistant; REVIEWER reserves it, which is what keeps a ``featured`` from being self-awarded.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/tellers/apis/tellers-api.md) - [All operations](https://skmtc.dev/tellers/apis/tellers-api/llms.txt) - [OpenAPI document](https://skmtc.dev/tellers/apis/tellers-api/revisions/fdaa0fa44a26?raw)