> For the complete documentation index, see [llms.txt](https://docs.colt.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.colt.net/on-demand/ja/on-demand-lso-portal/sbisuinbentorino.md).
# サービスインベントリの表示
## サービスインベントリ
お客様はサービス経由でライブサービスを表示できます **インベントリ**.
稼働中のすべてのEthernetスポーク接続とハブ（NNI）は、インベントリページに表示されます。
サービスID、回線ID、レンタル料金、または引き渡し／境界点の詳細などのサービスパラメータを表示するには、該当するサービスをクリックするだけで、すべてのパラメータを表示する新しいウィンドウが開きます。
スポークサービスのB端（お客様側）がデータセンター内にある場合、クロスコネクト注文に必要な委任状（LOA）は、を選択することでダウンロードできます **LOAを生成** オプション。
---
# 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.colt.net/on-demand/ja/on-demand-lso-portal/sbisuinbentorino.md?ask=&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.
