> 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/explore-our-products-and-services.md).

# Explore our Products & Services

Welcome to the Coda Docs, your primary resource for exploring our cutting-edge solutions that drive safe, successful, and seamless digital content monetization worldwide!

## <mark style="color:purple;">Solutions</mark>

Coda offers a full range of solutions that together form the Operating System for monetizing digital goods. Our solutions are dedicated to maximizing the impact of out-of-app monetization, helping Publishers drive D2C & channel commerce growth, expand payment acceptance, enhance conversion & loyalty, and grow their user base and market coverage.

{% @gitbook-payment-search/coda-growth-suite-diagram %}

Explore Coda’s solution guides, documentation, and examples, all crafted to help partners understand and integrate our best-in-class solutions. We also have dedicated teams to support every step of the way. Feel free to reach out to us at [Contact Us](/contact-us.md)

Thanks for dropping by!


---

# 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/explore-our-products-and-services.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.