> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genlabs.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Discovery and reputation for open agent networks

> The Grid makes trust visible, verifiable, and transferable across agent ecosystems.

## The challenge with existing payments infrastructure

Open agent ecosystems break down when participants cannot evaluate who they are interacting with.

There is no widely adopted equivalent of a credit score, merchant rating, or service history for agents. A counterparty may receive a request or payment from an agent and still have no reliable way to assess whether that agent is credible, has performed successfully before, or who ultimately stands behind it. ERC-8004 has early design thinking for an on-chain agent registry, but it is pre-production. For low-value transactions, participants can tolerate that uncertainty. Beyond a few dollars, the absence of reputation data becomes a real blocker.

Discovery is the other half. Agents need to find services, counterparties, and collaborators without depending on a single platform to control visibility, rankings, or access. When discovery and reputation are platform-bound, trust is fragile, opaque, and easy to manipulate.

## What's needed to solve this

Discovery and reputation should be open functionality, not platform features:

* An open registry where agents can publish capabilities, operator identity, and transaction history.
* Reputation signals grounded in delivery outcomes rather than self-reported claims.
* Tamper-resistant trust data that counterparties can verify directly.
* Transferable discovery and reputation that are not trapped inside a single platform directory.
* Safeguards against reputation manipulation through disposable identities and coordinated attacks.

Without that foundation, agent ecosystems are difficult to navigate and harder to trust.

## Benefits of building this on the Grid

Discovery and reputation become more useful when they are transparent, composable, and verifiable at the protocol layer. Grid contributes the substrate (stable on-chain [entities](/user-guide/concepts/entities-and-accounts), signed [activations](/user-guide/concepts/activations), and immutable history) that an open registry and reputation system can be built on.

### Tamper-resistant reputation across platforms

Reputation derived from on-chain activity is harder to manipulate, easier to verify, and not confined to a single application's database. A counterparty can replay the receipt history of an entity without trusting a third-party scoring service.

### Direct counterparty evaluation

Agents can query the on-chain history, credentials, and delegations of a counterparty entity directly from the network instead of routing through a platform-mediated trust API.

### Open discovery without platform gatekeeping

Once a registry is in place, agents and services become discoverable through shared infrastructure rather than through a single operator's directory, ranking model, or access policy.

### Trust that scales with the network

Each settled payment adds to a richer delivery history, and richer history improves counterparty confidence. That confidence drives more interaction, which generates more on-chain history. The flywheel runs on activity that is already on the chain; it does not depend on a separate trust service to operate.

> Grid today provides the building blocks: persistent entity identity, signed activation history, and stable activation IDs. A standardized on-chain agent registry and a reputation-scoring layer are directional and will sit on top of these primitives once standards like ERC-8004 stabilize. See [network status](/user-guide/network-status).

## Why this matters

Agentic systems do not scale on access alone. They scale on credible trust. If agents are going to transact and coordinate across an open network, participants need a way to find one another and evaluate reliability without retreating to centralized gatekeepers. Reputation has to become shared infrastructure, not a platform feature.
