> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/user-guides/using-the-oe-marketplace/editing-an-asset/update-the-assets-services/update-an-existing-service.md).

# Update an existing service

To update an existing service, perform the following:

1 . Click on the service. The service attributes are displayed.&#x20;

2\. You can change the following attributes:

* Service Name
* Service Description
* Service Language
* Price: <mark style="color:$info;background-color:$info;">Please note that if the service is paid, it cannot be changed to a free service and vice versa.</mark>&#x20;
* Payment Collector Address: By default, the payment collector address is the publisher's address; however, it can be changed to a different address.
* Provider URL: the Ocean Node that will encrypt the asset.&#x20;
* The asset's file: it is protected and not displayed in this field. If you want to change it, first, delete the existing file and then add the new one.
* Timeout
* Service State: select one of the following:&#x20;
  * Active - the service is consumable
  * EndOfLife - the service is not consumable
  * Deprecated - the service is not consumable
  * RevokedByPublisher - the service is not consumable
  * OrderingIsTemporaryDisabled - the service is not consumable
  * Unlisted - the service is not consumable
* Access Rules
* Consumer Parameters

<mark style="color:$info;background-color:$info;">For a description of each of these attributes, please review the</mark> [<mark style="color:$info;background-color:$info;">Publishing an asset</mark>](/user-guides/using-the-oe-marketplace/publishing-an-asset.md) <mark style="color:$info;background-color:$info;">page, step 3.</mark>&#x20;

3\. After the changes were made, click "**Submit**". A transaction request notification from Metamask appears on the screen. Press "**Confirm**".

<figure><img src="https://1789397093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH0zpgrXbeZ7u6UuCV9Gz%2Fuploads%2Fe4uwNENkWhavTCoCkn5U%2Fimage.png?alt=media&amp;token=2eb7fa05-e621-46c1-b7ee-0954dfd1ae34" alt=""><figcaption></figcaption></figure>

4\. A confirmation message is displayed on the screen. Click "**Back to Asset**" to return to the asset details screen.

<figure><img src="https://1789397093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH0zpgrXbeZ7u6UuCV9Gz%2Fuploads%2FcNNZyWV402HoGBrt3d7L%2Fimage.png?alt=media&amp;token=091d4272-6537-4a49-8aa6-c5f413ff84fd" alt=""><figcaption></figcaption></figure>

<mark style="background-color:$info;">Please note that from the time an asset is updated on the blockchain until it is indexed by the Ocean Node’s indexer, a delay may occur. This delay typically ranges from a few seconds to several minutes, depending on factors such as RPC endpoint performance, the current indexed block, and the machine’s processing capacity running the Ocean Node.</mark>


---

# 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.oceanenterprise.io/user-guides/using-the-oe-marketplace/editing-an-asset/update-the-assets-services/update-an-existing-service.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.
