# Proof-of-Human A managed **Proof-of-Human** service based on a user’s **on-chain behavior in your ecosystem**, with a **verification API** and **white-label UI** (including **badge levels**). Ideal for **bot-resistant access**, **airdrops/rewards**, and **governance**. *** ### What You Get #### PoH ID * **Personal PoH ID** derived from verifiable on-chain activity. * Issuance as a **Soulbound NFT** *or* a unique **registry record**. * **10 badge levels** (SBTs) granted at activity milestones. * **Verification API** to check ID status and parameters across your apps and backend. #### Full Branding * **Custom design & white-label interface** in your brand style. * **Custom subdomain** (e.g., `poh.yourbrand.xyz`) for a seamless user experience. #### Quality & Anti-Sybil Controls * **Behavior thresholds:** active days, unique contracts, gas spent, volumes, action sequences. * **On-chain quests** (swap, stake, vote, LP, bridge, etc.) that count toward PoH criteria. * Optional allow/deny lists and cooldowns to reduce farming. *** ### Why Projects Adopt PoH ID * **Identify real users** — exclude bots from campaigns, airdrops, and votes. * **Reputation-based models** — fair access tiers and rewards for meaningful contribution. * **Boost network activity** — users are motivated to complete actions to earn PoH ID and badges. *** ### How It Works 1. **Define criteria** — use RubyScore templates or your own formula (weights/thresholds). 2. **Ingest & evaluate** — we collect user activity and score it against your criteria. 3. **Issue credentials** — users mint **PoH ID** (SBT/registry) and receive **badge levels** (SBTs). 4. **Verify anywhere** — integrate PoH checks in your dApp, allowlists, and governance flows. 5. **Monitor** — optional dashboard to track adoption, quality, and level distribution. *** ### Deliverables * Deployed **PoH ID** (SBT/registry), **10 badge levels** (SBT), and **verification API** * **Branded UI** + **custom subdomain** * Documentation and integration support *** ### Integration Options * **Format:** issue the ID as a **Soulbound NFT** or as a **unique registry record**. * **Flexible verification criteria:** fully tailored to your project’s rules and thresholds. * **Branding:** custom design and a dedicated subdomain that matches your brand. * **Fast API setup:** production-ready in **\~15 minutes**. * **Multiple verification levels:** configurable targets such as **90%**, **99%**, or **100%** verification. * **Implementation time:** a ready-to-use **PoH dashboard within 3 days**. #### How It Works for You * **End-to-end delivery** — no need to build or maintain your own system. * A **simple API** and **ready-made reports** for campaigns and operations. * Use **RubyScore reference formulas** or **define your own verification rules**. * We **filter bots and fake accounts**, making your campaigns **transparent, fair, and effective**. *** ### Example * **Challenge:** Millions of testnet or quest participants flooding a leaderboard. * **Solution:** Implemented **Proof of Humanity (PoH)** to verify real participants. * **Outcome:** Successfully **filtered legitimate users** for the Token Generation Event (**TGE**), improving fairness and budget efficiency. *** ### Case studies * Somnia: RubyScore is one of the main PoH providers, filtering out 500,000+ bots from 1M+ quest participants using PoH ID and API (80,000+ PoH IDs minted, 1.2M+ reputation badges issued) * Linea: RubyScore became a key PoH provider, helping filter 243,000+ bots * Soneium: 50,000+ active wallets through IDs and badges; helped increase on-chain activity and identify engaged users *** ### Contact us * **Email:** * **Telegram:** --- # 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.rubyscore.io/for-partners/proof-of-human.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.