> For the complete documentation index, see [llms.txt](https://docs.kasko.io/kasko-frontend-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kasko.io/kasko-frontend-documentation/readme.md).

# README

In KASKO every client-facing app where the customer can purchase an insurance policy is called a webapp. The webapp consists of two important parts:

**1. Manifest**

Manifest is a JSON structure describing how an application needs to look and function. It has the definition of each individual page of the application and the logic for the flow. Read on in [the manifest guide](/kasko-frontend-documentation/getting-started/manifest.md).

**2. Field definitions**

If the manifest takes care of generating everything that is visible to the end-consumer, the field definitions is the description of the API that the application will interact with. It describes all the required pieces of information that must be collected and the validation rules for them. More about this in [the field definitions guide](/kasko-frontend-documentation/core-concepts/api-requests.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 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.kasko.io/kasko-frontend-documentation/readme.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.