> For the complete documentation index, see [llms.txt](https://yokifinance.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yokifinance.gitbook.io/docs/dollar-cost-averaging/creating-the-first-subscription.md).

# Creating the first subscription

{% embed url="<https://www.youtube.com/watch?v=dsfYPQGwvRE>" %}

The setup process for an automated purchase is very straightforward:

1. Connect the Web3 wallet
2. Change the network to the one on which your token is available (if necessary)
3. Choose the asset you'll be selling, likely a stablecoin, and purchase amount
4. Specify the purchase frequency (1h, 4h, 8h, 12h, daily, weekly, bi-weekly, monthly)
5. Specify the duration (or make it infinite)
6. Approve the spending limit
7. Voila, the automated transaction process is set up
8. The user receives the base asset with the average price for as long as his strategy is on


---

# 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://yokifinance.gitbook.io/docs/dollar-cost-averaging/creating-the-first-subscription.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.
