# What is RubyScore

**RubyScore** is an analytics platform and a decentralized reputation protocol for blockchains and wallets. It combines real-time on-chain activity with a vast and ever-expanding database of wallets, forming a unified **Reputation Layer**.

RubyScore indexes transactions across dozens of EVM networks, analyzing wallet activity through diverse interaction patterns in multiple ecosystems. On top of this data, a scoring engine aggregates signals and assigns each wallet a reputation score, consolidating activity from different networks into a single **Multichain Reputation Score (MRS)**.

For projects, RubyScore is a tool to filter out low-quality activity, ensure fair reward distribution, and build trust-based systems. For users, it is a way to build reputation and unlock new reward opportunities. **The Multichain Reputation Score, individual IDs, and APIs** turn raw data into actionable solutions for growth, marketing, and incentive design.

Simply put, **RubyScore** is the missing trust layer for Web3 — a way to identify, understand, and reward real users.<br>

## Vision

Imagine Web3 where decentralization is not only about network technology, but about experiences **shaped by your on-chain contributions**:

* Campaigns that reward **long-term behavior**, not meaningless clicks.
* Protocol access defined by your **reputation**, not your follower count.
* Ecosystems where **bots are filtered out by default**, not retroactively.

**RubyScore** transforms on-chain interactions into a **verifiable layer of reputation**, creating trust for blockchain ecosystems.


---

# 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/overview/what-is-rubyscore.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.