> For the complete documentation index, see [llms.txt](https://docs.demos.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.demos.global/onlymeid/overview/introduction.md).

# Introduction

OnlyMeID offers projects a universal, permissionless solution for Sybil Resistance. With OnlyMeID, projects and developers can protect on-chain interactions behind a "Human Gate" - guaranteeing that only wallets corresponding to unique humans may pass through.

Specifically, OnlyMeID services integrations through an offering called Biometric Proof of Personhood. Individuals may utilize their own biometric input (Selfie) to attest themselves as a unique, human operator of their associated wallet address.

It's important to differentiate this "Human Authentication" process from traditional KYC methods. KYC is a cumbersome, invasive process that requires a user verify themselves through sensitive documents like Government IDs. Although KYC can be used simply for Human Authentication, entities requiring this verification garner much more information specific to each individual, such as their citizenship, identification, name, date of birth, and so on.

Instead, OnlyMeID utilizes biometric input solely for the purpose of confirming whether or not a user wallet address is operated by a unique human. This is the *only* attestation required to achieve Sybil Resistance, and the utilization of a biometric input is the most straightforward, universal mechanism to achieve this attestation.

OnlyMeID is an on-chain mechanism that is compatible with existing user wallets. Projects that reference OnlyMeID do so on-chain, directly in the corresponding Smart Contract calls. Once a user has enrolled with OnlyMeID and minted their enrollment, they can interact with the entire universe of OnlyMeID integrations as they normally would with any other Smart Contract.

Beyond the original authentication, users may return to OnlyMeID to sign in again and "refresh" their enrollment on-chain. Projects with higher stakes needs, that want to confirm accounts are not sold or enrollments are not coerced, can require a recent refresh in addition to/in place of the original enrollment.

When users authenticate and further interact with OnlyMeID, they are granted the ability to write transactions on-chain which attest to these interactions. Users pay a small fee on top of gas when they do so, which is how Demos generates revenue.


---

# 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.demos.global/onlymeid/overview/introduction.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.
