> 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/jp/deal-making/create-a-deal-schedule.md).

# 取引スケジュールの作成

ストレージプロバイダーとの取引を行いましょう。まず、ディールプッシャーサービスを実行します。

```sh
singularity run deal-pusher
```

## 一度にすべての取引を送信する

小規模のデータセットの場合、すべての取引を一度にストレージプロバイダーに送信することができます。以下のコマンドを使用してこれを実現できます。

```sh
singularity deal schedule create <preparation> <provider_id>
```

ただし、データセットが大きい場合は、ディールプロポーザルの有効期限までに多くの取引をプロバイダーが処理することは困難かもしれません。そのため、スケジュールを作成することができます。

## スケジュール付きで取引を送信する

同じコマンドを使用して、取引がストレージプロバイダーにどれくらいの速さで、どれだけの頻度で行われるかを制御するための独自のスケジュールを作成することができます。

```sh
singularity deal schedule create -h
```


---

# 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/jp/deal-making/create-a-deal-schedule.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.