> For the complete documentation index, see [llms.txt](https://docs.synfutures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.synfutures.com/jp/oyster-amm/sekyuriti/saretasupottoindekkusu.md).
# 平滑化されたスポットインデックス価格
基礎となるオラクルから取得された生のスポット価格は、直接使用されるのではなく、特定の指数移動平均（EMA）手法を用いて価格変動が平滑化されます。これにより、スポットインデックス価格が容易に操作されることを防ぎ、市場の安定性が保たれます。価格変動は直接的にマーク価格に影響を与え、マーク価格はすべてのポジションの安全性を決定するため、これを平滑化することで市場の安全が確保されます。
---
# 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.synfutures.com/jp/oyster-amm/sekyuriti/saretasupottoindekkusu.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.
