> For the complete documentation index, see [llms.txt](https://docs.zeroauthority.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeroauthority.xyz/the-dao/standard-reputation-framework/clarity-and-json-implementation.md).

# Clarity & JSON Implementation

To create a **Reputation (REP) badge** using Clarity and JSON, you need to manage onchain logic with Clarity and define metadata with JSON.

### Clarity

{% content-ref url="/pages/6H4CLdiAcT2qG35f4bvK" %}
[Clarity Contract](/the-dao/standard-reputation-framework/clarity-contract.md)
{% endcontent-ref %}

The Clarity contract facilitates batch endorsements, allowing authorized users to issue badges to multiple recipients. It verifies the issuer's authority and manages the process of adding badges (endorsements) to users' profiles. Key functions include `add-badge` (adds a badge to a user) and `endorse` (issues badges to multiple users at once).

### JSON

{% content-ref url="/pages/RbQUjZACacvApi4ucTet" %}
[JSON Metadata](/the-dao/standard-reputation-framework/json-metadata.md)
{% endcontent-ref %}

The JSON metadata defines the badge's attributes, such as its name, description, image, and criteria. It helps visually represent the badge and provides context, like the number of events engaged in or the date issued.

Example structure:

```json
{
  "name": "Community Engagement Badge",
  "description": "Awarded for actively engaging in community events.",
  "image": "https://example.com/badges/community-engagement.png",
  "attributes": [{"trait_type": "Engagement", "value": "5 events"}]
}
```

Together, Clarity handles issuing the badge, and JSON defines its visual and contextual properties.