Platform
One memory. Every surface.
Connectors bring the knowledge in, a typed graph holds it, hybrid retrieval gets it back out, and MCP puts it where the work actually happens — the IDE, the assistant, the agent.
Ingestion
Get everything in, without a migration project.
350+ sources
A managed connector catalog, plus direct integrations for Gmail, Google Drive, Google Contacts, Notion, Confluence and HubSpot.
Files and documents
PDF, DOCX, XLSX, CSV, Markdown and images. Scanned documents go through OCR automatically — tables and formulas included.
Programmatic
One endpoint for text, markdown, HTML, JSON and code, with automatic, manual or hybrid routing into a department.
Authorise a source once at the organisation level, then grant it to specific workspaces. A team that should not see a source simply does not get a grant — no second authorisation required to withhold it.
Retrieval
Four engines, one answer.
You do not choose engines. The question is classified and the weighting follows from its class.
Vector
Semantic similarity across unstructured text.
Graph
Relationship questions no amount of text similarity will surface.
Temporal
Time-aware recall over bi-temporal facts.
Cache
Repeat answers in milliseconds, invalidated automatically on new content.
Agent-native
Memory where the work happens.
A memory product that requires a portal visit competes for attention. One that lives inside the IDE and the chat client becomes infrastructure.
Chordian exposes Model Context Protocol endpoints with a full OAuth authorization flow, so Claude Code, Cursor and other clients connect without a pasted key.
Scope is per-project: each Space is a scoped memory endpoint with its own credentials, so an assistant working on one repository cannot read another team’s material.
{
"mcpServers": {
"chordian": {
"url": "https://api.uni-flow.ai/mcp/space/spc_7f3a91"
}
}
}
# The client registers itself, opens the
# consent screen, and stores the token.
# Nothing is pasted.Also included
The unglamorous things enterprise procurement asks about.
Role-based access
Five roles and fifty-plus granular permissions with resource-scoped grants. Revoking access takes effect immediately, not when a token expires.
Immutable audit
Every privileged action recorded, tenant-scoped, with a trace id correlating it across services. Credentials are never written to it.
Credential lifecycle
Organisation-wide and per-memory keys, with scopes, IP allowlists, expiry, and rotation that mints the replacement before revoking the original.
Webhooks
Outbound delivery with signing, exponential retry and a dead-letter queue — so an outage on your side is recoverable, not silent data loss.
Usage accounting
Token and cost accounting for every model call, reconciled nightly against the provider. Usage on your own key is reported but never charged.
SDKs
Python and TypeScript, plus a documented REST surface with a live playground on every endpoint.
See the API before you commit.
Every endpoint in our documentation has a live playground. Fire a real request against a real environment without talking to anyone first.