> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/jp/keeper-msp/msp-developer-apis.md).

# MSP開発者向けAPI

これらのAPIやツールを使用して、MSP管理、アカウント管理、連携を自動化できます。

<table data-view="cards"><thead><tr><th>リソース</th><th data-card-target data-type="content-ref">ドキュメント</th></tr></thead><tbody><tr><td>請求、CSPM、SIEM連携の管理</td><td><a href="https://docs.keeper.io/enterprise-guide/jp/keeper-msp/msp-developer-apis/admin-rest-api.md">管理者向けREST API</a></td></tr><tr><td>MSPまたはディストリビューターとしてのアカウント管理</td><td><a href="https://docs.keeper.io/enterprise-guide/jp/keeper-msp/msp-developer-apis/account-management-apis.md">アカウント管理API</a></td></tr><tr><td>Keeperコマンダーを使用した管理対象企業の構成作成</td><td><a href="https://docs.keeper.io/enterprise-guide/jp/keeper-msp/msp-developer-apis/commander-template.md">コマンダーテンプレート</a></td></tr><tr><td>KeeperコマンダーCLIのインストールと使用方法</td><td><a href="https://docs.keeper.io/enterprise-guide/jp/commander-cli.md">コマンダーCLI</a></td></tr><tr><td>MSPおよび管理対象企業の管理に役立つその他のツール</td><td><a href="https://docs.keeper.io/enterprise-guide/jp/keeper-msp/msp-developer-apis/other-developer-tools.md">その他の開発者向けツール</a></td></tr></tbody></table>


---

# 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.keeper.io/enterprise-guide/jp/keeper-msp/msp-developer-apis.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.
