Live, not recorded
Nothing on this page is stored here. Seven requests to kinlab.ai produced everything below, and what came back is printed beside the path that produced it. Open the network panel and you will see them, alongside the page's own framework traffic. Kin's own repositories are the subject, because they are the ones we can show you in full. The counts are the hosted graph as it was last built, not a scan run when you loaded this page.
Reading the version...
Kin is the system of record for AI-written software.
Explore Kin's repository graph.
Start with a piece of code. The panel names it, its kind and the file the graph attributes it to, then lists the relationships that graph records around it and links to the source so you can check the answer. Pick a different entity in the drawing or the list and the panel asks the graph again. No checkout was read to answer any of it.
Asking the graph...
GET /api/v1/orgs/firelock-ai/repos
The organization as a graph
The same picture one level up, where a dot is a whole repository rather than an entity. Every line is a reference the graph reports running out of one repository and into another. The deployment lays the repositories out alphabetically around a ring, so where a dot sits carries no meaning and the lines are what to read. Most dots carry no line, and the note under the drawing says why. The rows behind both are printed as text further down.
Asking the graph...
GET /api/v1/orgs/firelock-ai/org-graph
What the hosted graph holds
Each row is a repository Kin has read into a graph, and each row's counts are the graph's own. The two figures above the table are those rows counted and added up on this page, not a total the graph reported. Nothing here walks a filesystem to answer.
Asking the graph...
GET /api/v1/orgs/firelock-ai/repos
References that cross a repository
These are separate Git repositories with separate histories, and a commit in one carries no record of the others. Each row below is a reference this deployment's graph reports running out of one repository and into another, with the confidence it carries and the number of entity-level relationships it stands for. What the graph holds is what you get: if its cross-repository index was not reachable when it answered, the panel says so above the rows rather than presenting a short list as a complete one.
Asking the graph...
GET /api/v1/orgs/firelock-ai/org-graph
Run it yourself
These are the requests this page made. They take no account and no token. If a number above looks wrong to you, this is how you check it.
curl -s https://kinlab.ai/api/kin-version
curl -s https://kinlab.ai/api/v1/orgs/firelock-ai/repos
curl -s https://kinlab.ai/api/v1/orgs/firelock-ai/org-graphThe reader routes are open because these repositories are public. Private ones answer nothing without a session, and the same code decides both.