For platforms

The hard part of your trust layer is already done

Your users stopped believing ratings a long time ago, and generic recommendations give them nothing to believe instead. Fixing that is a research problem: years of math on how trust and distrust move through a graph, and how to keep the result hard to game. We did that work. Point the engine at the endorsements you already record, and every user sees rankings backed by the specific people they trust, with a reason they can read.

The trust field view on a live demo: bars showing each research community's pull on one researcher's reading list, including communities he never joined
Live on science.uptrusthq.com: every community's pull on one researcher's reading list, including communities he never joined.
The problem you live with

Global ratings can be faked

A single score is easy to game. Bots, review farms, and brigading manufacture how many. Engagement ranking rewards outrage. Both wear down the community your platform depends on, and the recommendations they produce are generic for everyone.

Fake reviews

Paid and coordinated reviews add up to a high star count that says nothing about quality.

Brigading

A motivated crowd can bury a good contributor or lift a bad one, because volume is the only vote that counts.

Engagement ranking

Optimizing for time on site surfaces the loudest content, not the content people actually trust.

Generic recommendations

One popularity list for millions of people fits almost none of them well.

What changes

Rank by who, not how many

Every action on your platform, a follow, a review, a star, a purchase, becomes evidence of trust, or distrust, between two people. Trust spreads. You inherit, at a discount, the trust of the people you trust. Ranking is then weighted by who endorsed something, not by raw counts.

Personal

There is no single global score. The same items rank differently for every person, because rank depends on their own trust network.

Explainable

Every result carries a plain reason: trusted by people you trust. Users can see why something reached them.

Hard to manipulate

Attackers can manufacture how many, but they cannot manufacture who trusts them. The trust graph resists the usual attacks.

The engine also finds the communities in your graph and scores bridges: content that earns real endorsement from both sides of a disagreement. Engagement ranking splits a community to keep it clicking. Bridge scores give you the opposite lever, surfacing what holds it together. And the newest capability reads trust as a field. For any person it shows every community's pull on what they see, through which trusted people. "Why am I seeing this?" becomes a question you can actually answer.

Proof

Four live demos, one engine

Each demo runs the same engine over a different public record. Pick a viewer, see that person's ranking, then switch viewers and watch it reshuffle. Each one maps to a category you may already serve. Four so far. Any record of who endorses whom can be next.

For expert content and research libraries

science.uptrusthq.com

AI and ML research papers, from the citation graph.

The same papers. A different reading list for every researcher.

~25,000 papers, ~3,000 researchers

For developer tools and code collaboration

git.uptrusthq.com

Open source repositories, from the star graph.

The same repos. A different top list for every developer.

~35,000 repositories, ~8,000 developers

For knowledge bases and reference content

wiki.uptrusthq.com

English Wikipedia, from the editor thanks log.

The encyclopedia anyone can edit, ranked by editors you'd actually trust.

~236,000 articles, ~9,000 editors

For review sites and local discovery

review.uptrusthq.com

An educational demonstration on the Yelp Open Dataset, with trust inferred from taste agreement.

A research demonstration of trust-weighted local discovery, not a product.

~20,000 businesses, ~23,000 reviewers

No new user behavior

Runs on data you already have

The engine reads the signals your platform already collects: follows, reviews, stars, purchases, thanks. You do not need to ask users to do anything new. The demos prove this. Each one was built from a public record that already existed, with no new input from anyone.

That means recommendation, discovery, and reputation that are personal and explainable, using the history you have on hand.

Agent-ready

Built for the agents that choose for people

AI agents are starting to shop, read, and decide on people's behalf. To do that well, they need a trust source that is personal and permissioned, not one global rating.

UpTrust runs a live server that speaks MCP. With a person's permission, granted through OAuth, an agent can rank options, check trust as a band, find trusted voices on a topic, find bridges (the voices both sides of a disagreement still trust), and suggest introductions, all from that specific person's point of view. It works with Claude and any MCP-aware agent.

How it starts

Start with a pilot on one data category

We begin with one part of your data, follows, reviews, stars, or purchases, and run the engine over it. You see personalized, explainable ranking on your own content before you commit to more. From there we scope how the layer fits your product.