Bring your own AI. Keep EKOS as the knowledge layer.
You don't have to use our AI to search your knowledge. EKOS speaks the Model Context Protocol over an authenticated transport, so your own agents, assistants, and copilots can ask the governed layer and get cited, permission-checked answers.
The knowledge layer is the product. The chat is optional.
Most knowledge tools make you adopt their chatbot to search your own documents. EKOS works the other way: it exposes the governed layer over MCP, and your AI talks to it directly.
No EKOS chat required
EKOS is the knowledge layer, not a walled chat. Your Copilot, your internal assistant, your own agents, or any MCP client can search and ask the governed layer directly. You decide which interface your people use.
Your model, your rules
EKOS does not force you onto its models or its prompt. Connect the assistant you already run, and EKOS answers with the same permission-checked, cited passages your own Search workspace returns.
Same governance, every surface
Identity comes from the authenticated connection, not from anything the model writes. Tenant, organization, and corpus boundaries apply to agent traffic exactly as they apply to people.
Audited like everything else
Every tool call is audited against the machine identity that made it. You keep provenance and accountability when the question comes from an agent instead of a person.
What your agents can do, documented.
Each tool returns the same visibility-scoped passages, citations, and provenance your people see in the web workspace. No tool can reach beyond the authenticated tenant context.
search_knowledgeSearch the governed knowledge base with the same hybrid retrieval and visibility scoping as Direct Search.
rag_queryRequest a cited, evidence-grounded answer from the same pipeline that powers Ask EKOS.
trace_policy_to_evidenceWalk reviewed relationships from a policy to the procedures, controls, and evidence beneath it.
explain_relationship_provenanceInspect the excerpts, confidence, extraction method, and review state behind a relationship.
list_compliance_findingsList compliance findings filtered by framework and status.
get_evidence_for_requirementRetrieve the evidence artifacts linked to a regulatory requirement.
list_regulatory_changesInspect recorded regulatory change events and their classifications.
run_impact_analysisRun requirement, document, or entity impact analysis in either direction across the reviewed graph.
An agent cannot talk its way past your boundaries.
EKOS derives tenant and role context from the authenticated MCP connection before any tool runs. A tenant identifier inside a model-generated tool argument cannot override it, and a mismatch is recorded for audit.
Tenant-bound service accountsIssue expiring, individually revocable tokens with role context. The cleartext token is shown once and stored only as a hash.
Same REST credential modelOne bearer credential authenticates both the REST API and the streamable-HTTP MCP transport, so your integration team manages one identity model.
Audited activitySupported REST and MCP activity is audited against the machine identity, so agent questions leave an accountable trail.
Wire your agent to governed knowledge.
Bring the assistant your team already runs. We will issue a scoped token, connect it over MCP, and watch cited answers come back with the same permissions your people have.