> For the complete documentation index, see [llms.txt](https://mandarineframework.gitbook.io/mandarine-ts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mandarineframework.gitbook.io/mandarine-ts/mandarine-mvc/controllers.md).

# Controllers

{% hint style="info" %}
Definition of [Controller](https://mandarineframework.gitbook.io/mandarine-ts/mandarine-core/components/controller) & [Dependency Injection](https://mandarineframework.gitbook.io/mandarine-ts/mandarine-core/dependency-injection)  may be needed for this article
{% endhint %}

Controllers are the only type of component that can handle HTTP requests, which means, they are the only type of components that can handle the creation of *routes* and interpret the information a route is receiving or sending.

## Concepts

### Routing

As described above, controllers can handle the creation & utilization of routes. Routes are endpoints that will be requested by users. Routes can either send to the user or receive information from the user.

Routes are declared through the use of decorators on top of HTTP handlers.

### HTTP Handlers

HTTP handlers are methods that are executed when an endpoint is requested. They are directly connected with the declared routes as route decorators decorate these kind of methods.


---

# 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://mandarineframework.gitbook.io/mandarine-ts/mandarine-mvc/controllers.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.