> For the complete documentation index, see [llms.txt](https://docs.unbrowse.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unbrowse.ai/concepts/route-graph-as-asset.md). # The Route Graph as a Productive Asset A route graph is not a static registry; it is a productive asset with upkeep costs. The Maintenance Network paper makes this distinction directly: a registry is written once and assumed correct, while a route graph that carries real agent traffic produces ongoing value and therefore incurs ongoing cost. Routes fail, authentication flows change, schemas drift, and previously valid execution plans decay. The graph is worth something precisely because it is kept current, not because it was once complete. This framing matters because it explains why discovery alone is insufficient. A graph that only accumulates routes and never maintains them degrades toward noise as the web changes underneath it. The value is in the freshness, not the count. Treating the graph as an asset with upkeep is what makes the maintenance problem, and the accountability question that follows it, unavoidable rather than optional. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.unbrowse.ai/concepts/route-graph-as-asset.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.