What Is an Agent Knowledge Graph?

A knowledge graph stores facts as entities and the relationships between them — organisations, agents, actions and the edges that connect them — rather than as free text. Agents use one because a relationship is directly queryable: "who authorised this", "what does this org own", "which agents act for this human". The agentic internet is itself a knowledge graph across organisations, which is why a claimed edge is weaker than one both parties declare.

Stores

Entities and the edges between them

Query

Relationships, directly

Agentic use

Authority, ownership, provenance chains

Trust rule

A two-sided edge beats a one-sided claim

Edges are evidence

In a cross-organisation graph, a one-directional claim ("I am this org’s subsidiary") is something one party asserts. An edge declared from both ends is a fact two independent domains agree on, and that is what a resolver treats as evidence. Building the graph is easy; making its edges trustworthy is the whole problem.

Questions

How is this different from a vector store?

A vector store finds similar text; a knowledge graph answers relational questions exactly. Many agent systems use both — vectors to find, a graph to reason.

Is the estate a knowledge graph?

Yes. The directory federates per-organisation fragments of nodes and edges into one graph a stranger can traverse and verify.