> 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/publishing-an-asset/service-pricing.md).
# Service Pricing
22\. The Asset Level Credentials screen is displayed. In this screen, the asset's price is set.
An asset published on Ocean Enterprise can either be free or paid.
* **Publishing a free asset**: Click on the **Free** tab. Check the "I want this asset to be free. I understand network fees are still to be paid" checkbox and press **Continue**.
* Publishing a paid asset: Click on the **Fixed** tab.
* In the **Price** field, enter the price for the service.
* The currency of the price is displayed at the left side of the Price field
* Press **Continue**
---
# 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/publishing-an-asset/service-pricing.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.
