# KCD ? What is that

![](/files/-MZ2gVSiHM3Fhi0XtMRB)

###

![May change your code a bit ...](/files/-MYucJqmPAynT2r1asiB)

### So what's KCD ?

KCD is not a framework, it's not a router. KCD is a helper that simplifies your life for building maintainable and comprehensive REST applications. 

Its goal is to provide a way to write a beautiful handler without a boilerplate and translate it into a plain old HTTP handler.

This library is **opinionated** by default but **customizable** which means it uses some other libraries like Chi, Logrus... KCD is modular so each piece of the code that relies on a specific library can be changed.

### Is it painful to write your API in go?

What's the problem when you are building an API in Golang? You know the classic:

* Input marshaling from JSON
* Input from query parameters
* Input from path parameters
* Input validation
* Error handling
* Error logging
* Format response 

All this kind of stuff is boring and when you come from an established language like Java, PHP, Ruby each of these languages has its own framework with a battle-tested solution to handle all of the cases above.


---

# Agent Instructions: 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:

```
GET https://alexisvisco.gitbook.io/kcd/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.