TEtellers

Upsert Label

Create a label, or rename one and change who may attach it.

The only route that creates vocabulary, and reviewer-gated like everything else in this module — which is why nothing here screens what a label is called. An owner picks from what this produced; they never add to it.

label_id is normalised into a slug and then never rewritten: it is what every filter and every existing attachment names. Renaming is a display_name change.

put/agent/label/{label_id}

Request

  • Base URL
    https://api.tellers.ai (the document declares no server; this is the origin it was published from)
  • Auth
    none declared

Path parameters

label_idstring required

Headers

x-api-keystring nullable
authorizationstring nullable

Request body

display_namestring required
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.

Response

Successful Response

idstring required
display_namestring 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.

Changes

No recorded changes to this operation across all 2 revisions of this API.