Request a demo
Menu
Product
Capabilities
Request a demo
Integrations and API

Sources in. Identity across. Answers out.

EKOS is built to sit inside an enterprise stack: connectors feed one governed ingestion pipeline, your identity provider governs people, and the same knowledge layer answers through the web application, the REST API, and MCP.

Connectors

Every source, one governed ingestion path.

A connector only discovers changes and fetches content. Parsing, classification, versioning, provenance, and analysis happen in the same pipeline as a direct upload, so no source becomes its own silo. Sync is scheduled, manual, or webhook-accelerated, with resumable cursors and tombstones for deleted sources.

Available nowBuilt in

Direct upload

Upload PDF and Office documents into the durable ingestion workflow, with local OCR fallback for scanned PDFs and content-hash deduplication.

PreviewInternal source

Google Drive

Tenant-scoped OAuth, My Drive and shared-drive discovery, recursive folder scopes, incremental change sync, and Docs, Sheets, and Slides export into Office formats.

PreviewRegulatory source

OSCAL and NIST catalogs

Machine-readable NIST catalogs with stable control identities that survive republication.

PreviewRegulatory source

eCFR

Versioned Code of Federal Regulations text with section-level identity and change tracking.

PreviewRegulatory source

Federal Register

Daily rule announcements consumed from a resumable since-date cursor.

PreviewRegulatory source

FINRA rulebook and notices

FINRA-oriented sources covering the rulebook, with version diffing, and the Regulatory Notices feed.

Identity

Organizations, directory groups, and SCIM.

Verified identity context

Human access authenticates through your identity provider with verified JWT credentials. Tenant and actor context comes from the credential, never from caller-supplied headers or arguments.

SCIM 2.0 provisioning

Your directory pushes users and groups to EKOS's SCIM service provider: create, update memberships, and soft-deactivate. Administrators map directory groups to EKOS roles, and a deactivated user fails closed on the next request.

Organizations and corpora

One tenant serves many organizations without sharing every document. Corpus visibility, organization membership, and global reference subscriptions are enforced server-side across Search, Ask, the graph, and MCP.

Service accounts

Machine access uses tenant-bound service accounts with expiring, individually revocable tokens. The cleartext token is shown once and stored only as a hash, and one credential model covers both REST and MCP.

REST API

The whole loop, addressable over REST.

Everything the workspaces do is backed by the REST API, so pipelines and internal tools can ingest, search, review, and assemble proof programmatically.

Knowledge

Ingest, search, and ask across the governed estate.

  • Documents and versions
  • Search
  • Cited answers
  • Conversations

Governance

Review, connect, and trace change.

  • Review queue
  • Relationship graph
  • Impact reports
  • Duplicates

Compliance

Frameworks, findings, and assembled proof.

  • Frameworks and requirements
  • Findings
  • Evidence packages

Organization

Shape collections and their audiences.

  • Corpora
  • Controlled tags
  • Organizations
  • Directory groups

Access and audit

Machine identity and accountable history.

  • Service accounts and tokens
  • SCIM 2.0 provisioning
  • Audit events and export
MCP

MCP compatible: bring your own agents.

EKOS speaks the Model Context Protocol over an authenticated streamable-HTTP transport. Your assistants, copilots, and internal agents get governed access to the same knowledge layer, with identity derived from the connection and every tool call audited. An agent cannot switch tenants by passing a different identifier in a tool argument.

  • search_knowledge

    Search the governed knowledge base with the same hybrid retrieval and visibility scoping as Direct Search.

  • rag_query

    Request a cited, evidence-grounded answer from the same pipeline that powers Ask EKOS.

  • trace_policy_to_evidence

    Walk reviewed relationships from a policy to the procedures, controls, and evidence beneath it.

  • explain_relationship_provenance

    Inspect the excerpts, confidence, extraction method, and review state behind a relationship.

  • list_compliance_findings

    List compliance findings filtered by framework and status.

  • get_evidence_for_requirement

    Retrieve the evidence artifacts linked to a regulatory requirement.

  • list_regulatory_changes

    Inspect recorded regulatory change events and their classifications.

  • run_impact_analysis

    Run requirement, document, or entity impact analysis in either direction across the reviewed graph.

Service accounts and agent accessThe Search workspace
Next step

Wire a real agent to governed knowledge.

A demonstration can include the API and MCP surface: issue a scoped token, connect an agent, and watch cited answers come back.

Request a demonstrationExplore the capabilities