# Intro to Otterspace The Otterspace Protocol is a flexible and composable platform for building with non-transferable NFTs, which we call 'badges'. Badges are a status and reputation primitive used throughout communities, social applications, marketplaces, and media to represent achievements, skills, experience, roles, trustworthiness, and more. Badges are already an established concept in Web2, but why bring them on-chain? **Not-transferable tokens** We believe that primitives such as identity and reputation should not be sold to the highest bidder and are something that should be earned. Non-transferable tokens or Soulbound token standards are most well suited for this. Our protocol implement [EIP-4973](https://eips.ethereum.org/EIPS/eip-4973), the specification for Account Bound Token, for which we're an active contributor as well. **The benefits of on-chain Badges** By bringing badges on-chain, builders can benefit from Web3 composability. Existing integrations enable Badges to be used as token gates for Discord and Telegram, as well as in governance applications like Snapshot. Users' memberships, roles, status, and achievements become platformless, instead of being stuck in a specific application. While Web2 applications maintain user Badges in a centralized database, Web3 enables internet users to own their status and reputation and take it with them across experiences. **Why build with Otterspace?** We're building the Otterspace Protocol to solve all the core challenges related to issuing, interpreting, holding, and managing reputation primitives on-chain, so developers can focus on application-specific experiences. The Otterspace Protocol includes open-source contracts for direct integrations, as well as an API and no-code interface for ease of use. --- # 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://docs.otterspace.xyz/overview/intro-to-otterspace.md?ask= ``` 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.