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

# Case studies

### <img src="/files/tAAh0w7yeHeJsTXP7HRu" alt="" data-size="line"> **Somnia**: <https://rubyscore.io/somnia-id>

**Challenge:** Ahead of its airdrop and ecosystem launch, Somnia faced a massive influx of fake accounts and Sybil attacks. The goal was to filter out bots and keep only real users.

**RubyScore Solution:**

* Integrated **PoH ID** and **RubyScore API** for multi-chain wallet verification.
* Analyzed activity across multiple networks, including Ethereum.
* Verified key parameters:

  * actual wallet balance,
  * gas spent,
  * number of transactions,
  * unique contract interactions.

  and several other requests

**Result:**

RubyScore helped Somnia filter out more than **500,000 bots** and confirm the activity of real users. This ensured:

* fair token distribution,
* stronger trust in the ecosystem,
* higher engagement from genuine participants.

but also **triggered massive on-chain activity**, with over **1.4M users collecting reputation badges** Somnia.

### <img src="/files/RY7eD9DBgBCU8ToLFGsZ" alt="" data-size="line"> Linea: <https://rubyscore.io/attestation>

**Role:** RubyScore became one of the main providers of **Proof-of-Human (PoH) attestations** for the Linea ecosystem.

**Solution:**

* Issued PoH attestations based on **on-chain wallet activity** in Linea.
* Applied flexible verification criteria (balance, gas spent, transaction history, unique interactions).

**Result:**

* RubyScore helped Linea filter out more than **243,000 bots** and confirm the activity of real users.
* Ensured participation of only **verified users** in Linea’s quest campaign and airdrop.
* Increased **trust and transparency** across the ecosystem.
* Boosted **on-chain activity**, as users were motivated to verify their identity and collect reputation badges.
* As a result, more than **84,045 users** collected **Linea reputation badges**.

### <img src="/files/sJsFuid95aM0u0hxP1bD" alt="" data-size="line"> Soneium: <https://soneium.rubyscore.io/>

**Role:** RubyScore launched a **custom on-chain metrics dashboard** for Soneium to increase user activity and improve transparency across the ecosystem.

**Solution:**

* Developed a branded dashboard for tracking **wallet and network metrics** in Soneium.
* Integrated interaction flows with **ecosystem dApps** through RubyScore.
* User activity was linked to **Reputation ID and badges**, motivating participation across the ecosystem.

**Result:**

* Achieved a **significant increase in on-chain activity**: more than **40,000 wallets** engaged with various dApps to earn a Reputation ID.
* Provided projects with **transparent analytics** on network and wallet activity.
* Strengthened user motivation to interact with dApps, driving **higher engagement and retention**.

## <img src="/files/jvtHYECvrnU1kja4K88l" alt="" data-size="line"> MindoAI — Wallet Scoring API&#x20;

#### Objectives

* **Real-time wallet scoring** for user profiling and reputation signals across MindoAI products.

#### Solution

* Integration of the **RubyScore Multichain Wallet Scoring API** into MindoAI’s internal services.
* **Reduced time-to-value:** wallet scoring launched without running nodes or building custom indexers.

## <img src="/files/gd4EilkEnrzqnhK3mqOF" alt="" data-size="line"> WAGMI — Multichain Reputation Score API

#### Objectives

* Use the **Multichain Reputation Score (MRS) API** for user profiling, targeting, and gating across WAGMI products.

#### Solution

* Integrated the **RubyScore MRS API** into WAGMI’s backend to fetch per-wallet MRS and apply score thresholds to features, allowlists, and rewards.

#### Results

* **Reduced time-to-value:** reputation-driven flows launched without building in-house scoring or data pipelines.
* **Higher precision:** consistent cross-chain reputation signals improved access control and audience quality.


---

# 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 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/overview/case-studies.md?ask=<question>
```

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.