> For the complete documentation index, see [llms.txt](https://microgpt.gitbook.io/microgpt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://microgpt.gitbook.io/microgpt/how-it-all-works/micro-hackathons.md).

# Micro Hackathons!

<figure><img src="/files/eo154agPF43k2xYku4LU" alt=""><figcaption></figcaption></figure>

A MicroGPT hackathon is an exciting event designed to bring together developers, data scientists, and AI enthusiasts to explore and innovate with the MicroGPT model. \
\
These hackathons are vibrant and collaborative, usually running over 24 to 72 hours, where participants rapidly develop ideas and solutions. The main goals are to raise awareness of the MicroGPT brand, encourage its use among developers, and provide practical, hands-on experience with the software. \
\
By participating in workshops, receiving mentorship, and working on creative projects, attendees not only sharpen their skills but also help push the boundaries of what MicroGPT can achieve. These events are a fantastic opportunity to be part of a community driving the future of AI technology.\ <br>


---

# 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://microgpt.gitbook.io/microgpt/how-it-all-works/micro-hackathons.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.