> For the complete documentation index, see [llms.txt](https://docs.wicle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wicle.io/ai.md).

# AI

- [AI機能の提供ポリシー](https://docs.wicle.io/ai/policy.md): Wicle AIの有効化手順と、利用する生成AIサービス、データの取り扱い、禁止事項、免責事項を説明します。
- [MCPで外部AIサービスと連携する](https://docs.wicle.io/ai/mcp.md): 外部AIからWicleのデータを分析し、検索条件や通知などの設定を操作するためのMCPの接続方法、権限、データの取り扱い、レート制限を説明します。
- [チャットエージェント](https://docs.wicle.io/ai/agent.md): 表示中のデータを調べるクイック分析、データを深掘りする分析アシスタント、設定を相談する設定アシスタントの使い方を説明します。
- [AIレポート](https://docs.wicle.io/ai/ai-summary.md): AIが自動生成するレポートで、日次・週次・月次の流入やCV、定着などの変化を確認する方法を説明します。
- [ユーザー行動データの要約](https://docs.wicle.io/ai/summarize-event-data.md): ユーザー詳細で、ユーザー全体の行動傾向と日ごとの操作をAIで要約し、確認・再生成する方法を説明します。


---

# 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.wicle.io/ai.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.