> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coda.co/explore-our-products-and-services.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.