> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/manage-the-published-agents-catalog.md).

# Manage the Published Agents catalog

Catalog management controls how published agents appear in **Published Agents**. Labels help people find related agents. Visibility controls determine whether an entry appears in the catalog.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FLim5l0tCikdDCAEOQ7j5%2FG065.mp4?alt=media&token=63491000-18ed-48df-a885-151e75bbd024>" %}

## Before you start

Use an account with permission to manage the published-agent catalog.

## Open catalog management

Open Published Agents in the workspace dashboard.

![Published Agents management view](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/p1aWW7wjkvKlGE8Iofru/assets/g065-g065-01-manager.png)

Confirm the identity of each agent before changing its catalog settings.

## Hide an agent

Choose Edit, select the intended agent, and use Hide.

![Agent catalog visibility controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/A5t4faCMpcpRLMp6lInS/assets/g065-g065-02-hide.png)

Hiding changes catalog visibility. It does not by itself revoke access through a direct link.

Refresh the end-user catalog and check that the hidden card is absent.

![Agent catalog visibility controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/JXs9NdPrNlxEsgw03o13/assets/g065-g065-03-hidden-result.png)

Verify visibility from the view your audience uses.

## Restore a hidden agent

Open Hidden in catalog management and search for the agent by name.

![Hidden agent visibility restoration](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/1xnH37spOfQGbAXYZZZu/assets/g065-g065-04-hidden.png)

Check the selected card before changing its visibility again.

Select the agent and choose Unhide to restore its catalog visibility.

![Hidden agent visibility restoration](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/au7MfvemtgQBbebHuxXo/assets/g065-g065-05-unhide.png)

Refresh the end-user catalog to confirm the card is available.

## Create and assign labels

Use Add Label to create a useful category or select an existing label.

![Agent catalog label assignment](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/RuyUbCBKVTxppNarXAVr/assets/g065-g065-06-label.png)

Labels help users organize and find agents with related purposes.

Select the intended agents and use Assign Labels.

![Agent catalog label assignment](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/POL9cec98piXnOop7Pcp/assets/g065-g065-07-assign.png)

Check each card's label chip to confirm the assignment.

## Find agents by label

Use the label filter in the end-user catalog and review the resulting cards.

![Agent catalog label filters](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/ZadxJaVFfOdevQwGsJXj/assets/g065-g065-08-filter.png)

Confirm that the label brings together the intended agents.

Open a labeled card and check the destination interface.

![Agent catalog label filters](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/rTereIbYVHpFBeH7TiUM/assets/g065-g065-09-open.png)

Confirm its identity and welcome controls before directing users to it.

## Important behavior

Hiding an agent removes its catalog card. It does not revoke access through a direct link. Use interface security settings to control access.

## Continue

* [Interface authentication and access](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/interface-authentication-and-access.md)
* [Published Agents catalog](https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/published-agents-catalog.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/guides-and-quickstarts/interfaces-and-end-user-experiences/manage-the-published-agents-catalog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
