> For the complete documentation index, see [llms.txt](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/start-here/how-to-use-this-hub.md).

# How to Use Kurv University

Get the most out of Kurv University in the field.

Kurv University is organized the way a merchant conversation actually flows — from who Kurv is, to what they'd use, to the collateral you hand them, to how you close.

## Where things live

* [**Collateral Library**](/1roOeoqsO7DNkeNJG2xS/document-library/collateral-library.md) — the assets you actually send or hand over: product slicks, industry one-pagers, leave-behinds, and email templates. Start here when you need something to *give* a merchant.
* [**Products & Solutions**](/1roOeoqsO7DNkeNJG2xS/products-and-services/products-kurvmerchant.md) — the deep talking points behind every slick. Reach here when a merchant asks *"what would I actually use?"* or *"can Kurv do this?"*
* [**Selling Kurv**](/1roOeoqsO7DNkeNJG2xS/selling-kurv/selling-kurv.md) — your playbook: differentiators, ideal customers, objection handling, and how to talk pricing.

## Tips for the field

{% hint style="info" %}

* **Lead with a question, not a product.** "How do your customers pay you today?" opens every door.
* **Send the slick, then follow up.** Pair a [Product Slick](/1roOeoqsO7DNkeNJG2xS/products-and-services/products-kurvmerchant.md) with an email.
* **Keep** [**The 60-Second Pitch**](/1roOeoqsO7DNkeNJG2xS/start-here/the-pitch.md) **one tap away** for cold opens.
  {% endhint %}

{% hint style="warning" %}
This is an internal enablement resource for Kurv Agents and partners. Positioning here is for selling conversations — always confirm current pricing, rates, and terms in the merchant's signed agreement and your partner materials.
{% endhint %}


---

# 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://university.kurvpay.com/1roOeoqsO7DNkeNJG2xS/start-here/how-to-use-this-hub.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.
