The graph holds data but there's no structured way to ask questions of it — no neighborhoods, no
path finding, no lineage traversal — and nothing an agent can call to explore it.
Add a store-agnostic graph query API (neighborhood, path, lineage) behind a capability interface so
any backend can implement it, and expose it as agent tools using embabel-agent's @LlmTool /
ToolGroup convention. Queries respect edge authority, so low-trust edges can be filtered at query
time rather than at write time.
Use cases
- Ask for a proposition's neighborhood, the path between two entities, or the lineage behind a fact.
- Let an agent explore the graph through tools instead of hand-written queries.
- Filter low-trust edges out of a single answer at query time, leaving the underlying data intact for
other callers.
The graph holds data but there's no structured way to ask questions of it — no neighborhoods, no
path finding, no lineage traversal — and nothing an agent can call to explore it.
Add a store-agnostic graph query API (neighborhood, path, lineage) behind a capability interface so
any backend can implement it, and expose it as agent tools using embabel-agent's
@LlmTool/ToolGroupconvention. Queries respect edge authority, so low-trust edges can be filtered at querytime rather than at write time.
Use cases
other callers.