> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-webstore/steps-to-launch-your-web-store/step-1-add-title-and-pricing-info.md).
# Step 1: Add Title and Pricing Info
The process begins by adding the title on the [Coda Portal](https://bit.ly/4aNqHRf). Coda is happy to handle this this setup step for you, or the partner pay opt to do so themselves. Find the complete guide on [How to Add a new Title](/codashop-and-distribution/add-your-title-app.md).
In order to begin select **Custom Commerce** as the service type.
Once the title is added, Coda will configure the Title content and in-app products including pricing. The pricing details are provided by the partner and reviewed by Coda’s team before configuration. Refer to our guides below on how to [Submit Title Content](/codashop-and-distribution/add-your-title-app.md) and [Product data](/codashop-and-distribution/submit-inventory-skus-details.md).
---
# 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.coda.co/coda-webstore/steps-to-launch-your-web-store/step-1-add-title-and-pricing-info.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.