> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/depin/iotex-depin-modules/w3bstream/build-with-w3bstream/deploy-to-w3bstream/interacting-with-projects.md).

# Interacting with Projects

As the owner of the project NFT, you have the ability to query and interact with your W3bstream project at any time. Below are the operations you can perform on your W3bstream project:

## **Start the Project**

To start your project, use the following command:

```sh
ioctl ws project resume --id 1234
```

## **Query the Project** 

To query the status or details of your project, use the following command:

```sh
ioctl ws project query --id 1234
```

## **Set Required Prover Amount for the Project**

By default, the prover amount that processes the project's tasks is set to one. You can customize this amount using the following command:

```sh
ioctl ws project attributes set --id 1234 --key "RequiredProverAmount" --val "your expected amount"
```

## **Stop the Project**

If you need to stop the project's task processing, use the following command:

```sh
ioctl ws project pause --id "your project id"
```


---

# 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.iotex.io/depin/iotex-depin-modules/w3bstream/build-with-w3bstream/deploy-to-w3bstream/interacting-with-projects.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.