> For the complete documentation index, see [llms.txt](https://satea.gitbook.io/satea/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://satea.gitbook.io/satea/project-setup-guide/grass.md). # Grass ## **Step 1: Purchase a** Grass **node** 1. Login to [app.satea.io](http://app.satea.io) and select Grass 2. Select the number of nodes and node duration After confirming that there are no errors, please follow the instructions to complete the payment. ## **Step 2: Register your Grass account and export your user ID** Finish registration and login on Grass official website:
After logging in, enter the Grass Dashboard interface. Enter F12 on the keyboard (fn+F12 on MacOs) to enter the developer tools.
After refreshed the webpage, click "Network", "Fetch/XHR", "retrieveUser", and "Preview" in the boxes to enter the interface shown below.
In the code below the Preview in the image, you can see the content in the yellow box, "userID". Copy the number after userID. ## **Step 3: submit your user ID to bind your devices** Please go to the "open-ticket" channel in the Satea official Discord: to submit your Grass userID.
Submission content: * Satea registered email * Grass userID If the same account has purchased multiple Grass nodes, please send the userIDs of all nodes separately. After the userID is sent, the Grass node will be configured within 2 working days without any other operations. After the configuration is completed, you can see that the new device has been successfully added in "Your Networks" at the bottom of the Grass Dashboard, and it will show "Connected". You can confirm that the online time of the new device is consistent with the deployment time at "Time Connected".
The above completes the node configuration of Grass. --- # 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://satea.gitbook.io/satea/project-setup-guide/grass.md?ask=&goal= ``` `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.