Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/org-quicko/skillset/llms.txt

Use this file to discover all available pages before exploring further.

The Tags API exposes the Registry’s Tag catalog — the shared set of short labels that Resources can carry for browsing and filtering. Listing all Tags requires no authentication. Renaming a Tag (which affects every Resource currently carrying it) requires Admin role.
Attaching or removing Tags from a specific Resource is done through PUT /api/resources/:id/tags, not here. This API covers the catalog itself: listing Tags and renaming them.

​
Endpoints at a glance

MethodPathAuthDescription
GET/api/tagsNoneList all Tags
PATCH/api/tags/:idAdmin+Rename a Tag

​
List all Tags

GET /api/tags
Returns every Tag in the Registry catalog. No authentication required. The CLI and MCP server call this endpoint to resolve a Tag name to an id before filtering the resource catalog.

​
Response fields

​
items
array
All catalog Tags. Each entry has:
curl https://registry.example.com/api/tags

{
  "items": [
    { "id": "018f1234-abcd-7000-8000-000000000001", "name": "typescript" },
    { "id": "018f1234-abcd-7000-8000-000000000002", "name": "react" },
    { "id": "018f1234-abcd-7000-8000-000000000003", "name": "testing" }
  ]
}
To filter the resource catalog by a Tag name (rather than id), call GET /api/tags first, find the matching Tag by name, and pass its id as the tag_id query parameter on GET /api/resources. The CLI and MCP server do this resolution automatically.

​
Rename a Tag

PATCH /api/tags/:id
Changes the name of an existing Tag. Requires Admin role. Because Tags are stored by id and every Resource references the id, a rename is immediately visible everywhere the Tag is attached — no Resource needs to be republished.

​
Path parameters

​
id
string
required
UUID of the Tag to rename.

​
Request body

​
name
string
required
New name for the Tag. Must be lower-case, URL-safe, and no longer than 32 characters. Must not already be the name of another Tag.

​
Response

Returns the updated Tag object: { "id": "...", "name": "..." }.

​
Error codes

CodeStatusWhen
not_found404No Tag exists with that id.
tag_name_conflict409Another Tag already has that name.
validation_failed400The new name failed the Tag name rules.
curl -X PATCH https://registry.example.com/api/tags/018f1234-abcd-7000-8000-000000000001 \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{ "name": "react-18" }'

Build docs developers (and LLMs) love

Get started for freeTalk to us