---
title: >-
  Intentface OS for agents — Read by agents, tended by agents. Approved by
  people.
description: >-
  Intentface OS for agents: the MCP tool surface and scoped API, the orient call
  that maps a workspace in one round trip, the AI Janitor that keeps the index
  tidy, the health score agents feed, and the mounts and syncs that connect
  external systems.
url: 'https://www.intentface.com/os/for-agents'
site: Intentface
---

# Intentface OS for agents

> The agent-native side of Intentface OS.

**Read by agents, tended by agents. Approved by people.**

Intentface OS speaks MCP and a scoped REST API. A connecting agent orients itself in one call, searches in your team's vocabulary, and reports what it couldn't find. Underneath, a curatorial pass keeps the index in order, and the systems your agents depend on are mounted or synced into the same workspace.

MCP · REST API with OpenAPI spec · Scoped, expiring keys

## An agent's first call tells it everything

Instead of guessing at filenames, a connecting agent calls orient and gets the actual lay of the land: every folder with summaries, every file with an outline and a stable reference, and the vocabulary this organisation uses, all before reading a single document.

MCP tool surface:

- `orient` — Workspace map, file summaries, and the concept index spine
- `search` — Concept-aware search across every file
- `read_file, edit_file, create` — Read and write markdown, single or batched
- `query_db, write_db` — Query and update structured tables with SQL
- `concept_resolve, concept_search` — Resolve a term to what the workspace actually calls it
- `share_file, submit_feedback` — Publish artifacts and report back

## A workspace that tends itself

Knowledge bases rot when upkeep depends on people remembering to do it. Intentface OS assigns the chore to a curatorial pass that runs quietly in the background: roughly 90% machine, 10% human, and that 10% is veto power, not workload.

- **Merges and splits concepts** — Twin terms that emerged separately become one; overgrown ones split.
- **Lets noise go dormant** — One-off terms and unused concepts stop widening your searches.
- **Writes scope notes** — Important concepts get a one-line definition, backfilled automatically.
- **Detects conflicts** — Two live documents disagree on a fact? It asks exactly one question.

The Janitor suggests, the human disposes. It never deletes and never reverts a human edit.

### Your knowledge has a pulse

Every search, read, and edit feeds a live health score, and the agents working in the workspace report what they couldn't find, so gaps surface before any human notices them.

- **One score, real evidence** — Structure, search, context quality, and activity each score 0 to 100. The composite tells you at a glance what's healthy and what's dragging, with the evidence one click away.
- **Agents file the friction** — When a search comes up empty or a document contradicts itself, the agent doesn't shrug. It flags a content gap or an outdated page through submit_feedback, failed query attached.
- **And the workspace tends to it** — Flagged issues become work: the missing page gets drafted, orphans get linked, the stale copy gets superseded, all done by workspace agents and approved by a human clicking yes.

## A knowledge base shouldn't be an island

Intentface OS doesn't have to contain everything. It has to know where everything is. Mount external sources into the index, sync live systems into local tables, and let concepts point to the workflows and tools that actually get the job done.

- **Mounted, not copied** — Articles in a GitHub repo, marketing pages, a partner wiki: external sources mount straight into the search index. The content stays where it's authored; agents surface it like any native file.
- **Synced, not fetched** — Sandboxed pipelines pull live systems into local, read-only tables: fast, rate-limit-proof, and when a provider changes, exactly one pipeline needs repair. Pipeline code never sees credentials.
- **An index of skills** — Beyond facts, the index covers skills: meta-knowledge of how things get done and where the pieces live. An agent asking “how do we publish a release?” gets the runbook, the repo, and the right connector, not a guess.

Connectors: Slack, Clockify, Zero CRM, Circleback, Perplexity. External mounts, webhooks, and more.

Point your agent at the workspace. It will know where to start. Claude Desktop, Claude Code, any MCP client, or your own code against the API: the first call is orient, and the rest follows.

Request early access: https://www.intentface.com/contact

Product overview: https://www.intentface.com/os.md