Find context for a review
Identify a graph path and related source material for the current task.
Required capabilities- 01
graph_traversal - 02
vector_search
A research agent finds the sources. An analysis agent compares them. A review agent needs both the conclusion and the evidence behind it. Minds helps you organize each agent’s context, share selected knowledge, and find the capabilities the next task requires.
Capability dispatch
Identify a graph path and related source material for the current task.
Required capabilitiesgraph_traversalvector_searchalphagraph_traversalMatched to requirement 01org_internalalpha.localbetavector_searchMatched to requirement 02org_internalbeta.localgraph_traversalalpha.local/v1/queryvector_searchbeta.local/v1/queryThe router returns a plan. Your application dispatches the work and enforces access policies.
Register what each agent can do, then ask the Knowledge Router to find matching agents for your plan. For a research review, that could mean one agent to follow citation links and another to search the source material. Your application uses the returned route to coordinate the work.
Context
Use an agent-scoped namespace to organize its records and requests. Configure authorization separately to control access to those records.
Capabilities
Register the tasks an agent can handle, along with its identity and endpoint, so the router can find it.
Knowledge
Write useful relationships to a graph that authorized agents can query, while keeping agent-specific context separately scoped.
Routing
Describe the capabilities a task needs. The router returns matching agent endpoints for your application to call.
A routing plan identifies where a task can go. Agents still manage their own execution, and your access policies determine which knowledge they can use or share.
Visibility
A capability record can carry a public, organization-internal, or private visibility label. Enforce the corresponding access rules in your deployment.
Identity
Registration includes an identity proof that the router’s configured trust adapter validates.
Execution
Inspect the returned route and dispatch the task through your application. A route identifies a destination; executing and completing the work remain part of your workflow.
Memory
Keep an agent’s events and procedures in its own scope, then publish selected knowledge through the shared graph according to your access policies.
This application excerpt registers two agents and requests a route for their capabilities. It assumes a configured KnowledgeRouter gRPC adapter with secure transport and identity proofs accepted by your trust policy. Memory storage and task execution are separate integrations.
// router is your configured KnowledgeRouter gRPC adapter.
// Its methods below wrap the corresponding RPCs as promises.
const alphaToken = process.env.ALPHA_ROUTER_IDENTITY_TOKEN;
const betaToken = process.env.BETA_ROUTER_IDENTITY_TOKEN;
if (!alphaToken || !betaToken) throw new Error("Configure agent identity proofs");
await router.registerCapability({
descriptor: {
agentId: "alpha",
dataspaceId: "desk",
host: "alpha.local",
queryEndpoint: "/v1/query",
capabilities: ["graph_traversal"],
visibility: "org_internal",
identityProof: { scheme: "jwt", payload: Buffer.from(alphaToken, "utf8") },
},
});
await router.registerCapability({
descriptor: {
agentId: "beta",
dataspaceId: "desk",
host: "beta.local",
queryEndpoint: "/v1/query",
capabilities: ["vector_search"],
visibility: "org_internal",
identityProof: { scheme: "jwt", payload: Buffer.from(betaToken, "utf8") },
},
});
const plan = await router.routeTask({
plan: {
requirements: [
{ capability: "graph_traversal" },
{ capability: "vector_search" },
],
},
});
// Inspect plan.steps, then dispatch through your application.A registered capability includes the agent’s identity, visibility, and endpoint. A returned plan identifies the steps your application can dispatch.
Start with two agents, define what each can do, and connect the knowledge they need for a shared task.