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

# Badges

Badges are milestone markers recognition for specific things that happened at specific moments. They live in your Achievements tab and are earned by everyone in the ecosystem, not just learners.

Karma grows cumulatively. Levels mark transformation. Badges do something different. A badge says one specific thing: *"This happened. I was there. I did that."* Not how much you've contributed overall. Not who you've become over time. A specific moment. A specific achievement. Permanently recorded.

### <mark style="color:$primary;">Where Badges Live</mark>

All your badges live in the **Achievements tab** on your μLearn profile. Every badge you earn is permanently visible there to you, to your peers, and to anyone who views your profile.

### <mark style="color:$primary;">What Badges Recognize</mark>

Badges are allocated across three categories:

<table><thead><tr><th>Badge Type</th><th width="181.66668701171875">What It Marks</th><th width="203.9896240234375">Examples</th></tr></thead><tbody><tr><td><strong>Event Badges</strong></td><td>Participation or contribution in a specific μLearn event</td><td>In50Hours participant, Permute attendee, Hackathon contributor</td></tr><tr><td><strong>Level Badges</strong></td><td>Reaching a specific level milestone</td><td>Level 3 achieved, Level 5, The Arena unlocked</td></tr><tr><td><strong>Skill Badges</strong></td><td>Demonstrated proficiency in a specific skill area</td><td>UI/UX certified, Web Dev validated</td></tr></tbody></table>

### <mark style="color:$primary;">Who Gets Badges</mark>

Everyone in the μLearn ecosystem not just learners.

**Learners** - earn badges for events attended, levels reached, and skills demonstrated.

**Mentors** - earn badges for completing μMent cycles, contributing to specific programs, and sustained volunteer engagement.

**Campus Chapters** - earn badges for hosting events, reaching participation milestones, and contributing to the ecosystem collectively.

**Companies** - earn badges for active collaboration with μLearn challenge hosting, hiring through Launchpad, mentorship contribution, and partnership milestones.

### <mark style="color:$primary;">How Badges Differ from Karma and Levels</mark>

These three signals each tell a different story:

<table><thead><tr><th width="195.66668701171875">Signal</th><th width="332.32281494140625">What It Says</th></tr></thead><tbody><tr><td><strong>Karma</strong></td><td>This is how much I've contributed overall across all dimensions, cumulatively. It acts as the Skilling Currency.</td></tr><tr><td><strong>Level</strong></td><td>This is who I've become the stage of transformation I'm at.</td></tr><tr><td><strong>Badge</strong></td><td>This specific thing happened, I was there, I did that, at that moment.</td></tr></tbody></table>

A profile with high Karma, Level 6, and a collection of specific event and skill badges tells a complete, three-dimensional story of a contributor.

No single signal tells the whole story. All three together do.

→ To understand how Karma and Levels work together, go to [**Karma**](/core-concepts/karma.md) and [**Levels**](/core-concepts/levels.md)

→ To see your full profile including Achievements, go to [**μID**](/core-concepts/mid.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/core-concepts/badges.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.