# Route Trust Tiers A healthy Unbrowse graph supports at least two layers: open routes and higher-trust routes. ## Open routes Open routes are the low-friction layer. Anyone may publish or improve route knowledge, no bond is required, and they are ranked by observed utility and performance. They still earn contributor rewards when used and remain suitable for general, low-risk traffic. This layer preserves the honesty of the wedge: discovery stays open, adoption stays simple. ## Higher-trust routes Some routes eventually matter more than others: authenticated workflows, high-value transactional paths, routes that need freshness guarantees, reliability-sensitive automations, enterprise-facing execution paths. For these the graph needs a stronger trust model than simple observation. A route should be able to carry an explicit, accountable maintenance claim, which may involve reputation, periodic verification, challengeability, and where justified optional bonding. ## What the user sees The demand side stays simple. Pricing is stable-denominated, route selection is low-friction, and the user never has to hold a native asset or think in token units to decide whether a route is worth using. The graph is experienced as a layered trust surface: * **open** * **trusted** * **premium** The complexity of accountability lives on the supply side, not the demand side. That is what preserves the product wedge while still letting the graph develop serious maintenance guarantees where they are needed. ## Ranking stays grounded in quality Ranking should reflect success rate, freshness, authentication validity, latency, failure-recovery behaviour, challenge history, repeat usage, and value saved relative to rediscovery. It should not be ordered by capital size. If bonding exists it affects trust-tier eligibility and accountability, never simple ranking by stake, because a graph where the highest bidder is mistaken for the highest-quality route is the opposite of what Unbrowse should become. --- # 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.unbrowse.ai/concepts/route-trust-tiers.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.