> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/frequently-asked-questions/why-do-i-see-single-glance-endpoint-in-ui.md).

# Why Do I See Single Glance Endpoint In UI?

## Problem

Under the ' **Access & Security**' tab of UI, the **Glance** endpoint is pointing towards the endpoint of a single **Glance** host in 'API Access' instead of all the **Glance** Hosts API endpoints.

## Environment

* Platform9 Managed OpenStack - All Versions
* Glance

## Answer

This is by design. The single **Glance** endpoint visible in UI can be used to make direct API calls for that endpoint. Similarly, the other **Glance** endpoints listed by the below command can be used to make the API call for the respective **Glance** nodes.

{% tabs %}
{% tab title="None" %}

```none
# openstack endpoint list --service glance
```

{% endtab %}
{% endtabs %}

## Additional Information

The **Nova** and **Cinder** services use **Glance** clustering. This ensures that the best possible endpoint is chosen by the service during runtime. You can get the list of currently available **Glance** cluster endpoints by running the below command.

{% tabs %}
{% tab title="None" %}

```none
# openstack endpoint list --service glance-cluster
```

{% endtab %}
{% endtabs %}


---

# 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://platform9.com/kb/pmo/frequently-asked-questions/why-do-i-see-single-glance-endpoint-in-ui.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.