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

# 初めての方へ

- [Ripple とは？](https://docs.alphaus.cloud/ripple/guide/about-mobingi-ripple.md)
- [Ripple のセットアップ](https://docs.alphaus.cloud/ripple/guide/set-up.md)
- [Hourlyレポート解析の有効化](https://docs.alphaus.cloud/ripple/guide/set-up/prepare.md): Ripple の利用を開始するにあたり、事前に必要な設定をご説明します。
- [顧客登録](https://docs.alphaus.cloud/ripple/guide/set-up/register-customer.md)
- [請求書設定](https://docs.alphaus.cloud/ripple/guide/set-up/invoice-setting.md)
- [毎月の請求書発行の手順](https://docs.alphaus.cloud/ripple/guide/routine.md)
- [1. 請求データ確定の連絡](https://docs.alphaus.cloud/ripple/guide/routine/click-button.md)
- [2. 為替レートの登録](https://docs.alphaus.cloud/ripple/guide/routine/set-conversion-rate.md)
- [3. ショットの費用を請求に含める](https://docs.alphaus.cloud/ripple/guide/routine/add-fee.md)
- [4. 請求書の作成](https://docs.alphaus.cloud/ripple/guide/routine/issue-invoice.md)
- [5. 発行した請求明細の確認とダウンロード](https://docs.alphaus.cloud/ripple/guide/routine/download-csv.md)
- [6. エンドユーザーに請求明細を提示](https://docs.alphaus.cloud/ripple/guide/routine/show-billing-statement.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.alphaus.cloud/ripple/guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.