> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/kr/cli-reference/run/deal-tracker.md).

# 거래 추적기

{% code fullWidth="true" %}

```
명령:
   singularity run deal-tracker - 모든 관련 지갑 거래를 추적하는 거래 추적기 시작

사용법:
   singularity run deal-tracker [command 옵션] [arguments...]

옵션:
   --market-deal-url value, -m value  ZST 압축 상태 거래 json에 대한 URL입니다. Lotus API를 사용하려면 빈 값으로 설정하십시오. (기본값: "https://marketdeals.s3.amazonaws.com/StateMarketDeals.json.zst") [$MARKET_DEAL_URL]
   --interval value, -i value         새로운 거래를 확인하는 간격입니다. (기본값: 1h0m0s)
   --once                             한 번 실행 후 종료합니다. (기본값: false)
   --help, -h                         도움말 보기
```

{% endcode %}


---

# 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://data-programs.gitbook.io/singularity/kr/cli-reference/run/deal-tracker.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.