01 — code browse
Browse the source.
Open the fixture repo home to see commit history, branch list, and the indexed file tree. Every file here was cloned from a real Git remote.
See it live.
Six stops on a public, anon-readable fixture repo. No account needed. Every link below opens a real surface running on rethunk/kg-cross-lang-smoke-utdjor.
02 — symbol search
Search across the index.
The symbol index covers every function, type, and variable across Go and TypeScript. Try searching for "AssignSeat" to see callers, definitions, and cross-file edges in one query.
03 — knowledge graph
Query the project graph.
Every push rebuilds a queryable symbol graph: callers resolved, cross-language edges indexed, impact chains traced. Open insights to explore the live graph for this repo.
04 — wiki
Read the KG-backed wiki.
Wiki pages on src.land are tied to the knowledge graph. API reference blocks and coverage reports update automatically when the code changes. Open the wiki to browse it.
05 — agent access
See what an agent receives.
Agents connect over the MCP protocol using a scoped bearer token. The same symbol index, wiki, and graph the tour showed you is what an agent reads in real time. No scraping, no polling.
06 — audit trail
Every action leaves a row.
Human pushes and agent reads both land in the same append-only audit log, keyed by namespace, actor, and action. Open the audit guide to understand what is captured and how long it is retained.
Start with your own repo
Push once. Get the graph.
One repository is enough to evaluate the knowledge graph, audit log, and agent access surface.