> 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/create-a-new-service.md).
# Create a new service
To create a new service, perform the following:
1\. Click on the "**Add a new service**" button. The "Add a new service" form is displayed.
2\. Fill in the following fields:
* Service Name
* Service Description
* Service Language
* Price: If you want the asset to be free, set the price to zero. For a paid asset, set the price to a value other than zero.
* 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.
* The asset's file
* Timeout
* Access Rules
* Consumer Parameters
For a description of each of these attributes, please review step 3 of the [Publishing an asset](/user-guides/using-the-oe-marketplace/publishing-an-asset.md) page.
3\. After the service's attributes are entered, click "**Submit**". A transaction request notification from Metamask appears on the screen. Press "**Confirm**".
4\. A confirmation message is displayed on the screen. Click "**Back to Asset**" to return to the asset details screen.
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.
---
# 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/create-a-new-service.md?ask=&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.
