{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/company-knowledge.fresh-document/",
    "json": "https://www.anchorterminal.com/niches/company-knowledge.fresh-document/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/company-knowledge.fresh-document/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/company-knowledge.fresh-document/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 7 | 22 | 11 | 4 |\n\n## What counts as done\n\nA document created or changed at time T is returned by search within a stated lag, including edits, moves and thread replies, and each result carries its last-updated time.\n\nMeasured, for our own tests: the lag meets the 15-minute target.\n\nHow agents ask for it: the new policy went up this morning, what does it say; has anyone replied in that thread since; find the file Sam just moved into the shared folder\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Dust (Permutation Labs)**: Connections sync automatically and docs say an update usually takes a few minutes, and documents carry a timestamp. No per-connector interval or handling of moves and thread replies is published, so the 15-minute target is a claim, not a figure.\n- **Gemini Enterprise (Google LLC)**: Federation reads sources live, but ingested stores sync incrementally every 3 hours at best, and incremental syncs miss deletions and identity changes, so the 15-minute target holds only for federated sources, with lower search quality.\n- **Glean (Glean Technologies, Inc.)**: Refresh rates are published per connector (Slack and Confluence event-triggered, Drive incremental every 3h, Confluence 1h) and results carry updateTime, but Glean says events give no time-to-search guarantee, so the 15-minute target isn't shown.\n- **Guru (Guru Technologies, Inc.)**: Results carry lastModified and cards written in Guru are native, but connected sources sync with only a lastSyncedDate and sync status; no sync interval or lag per connector is published.\n- **Hexis Cloud (Bevelites GmbH)**: Writes through Hexis land in its clone at once, and POST /api/sync/\u003cbranch\u003e from a webhook pulls outside pushes within the request; without the hook a push isn't seen until Hexis touches the branch. Search hits carry no updated time; list_file_changes gives who and when.\n- **Onyx (DanswerAI, Inc.)**: Refresh Every defaults to 30 minutes, results carry updated_at and accept time_cutoff, and Federated Slack searches live. But in-thread Slack replies (acc-22) and moved SharePoint files (acc-23) are never indexed, silently, and Ingestion API documents don't reach MCP (acc-38).\n- **Lens (Thought Industries) (Thought Industries, Inc.)**: Answers reflect each source's last sync: manual on Free, weekly on Pro, twice weekly on Pro+, daily on Enterprise. POST /v1/sources/{id}/sync starts a background sync, but results carry no updated time, only the source's lastSyncedAt.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Cohere North (Cohere Inc.)**: Connector sync cadence and result timestamps would be in the closed developer docs; the public pages name connectors but no sync interval.\n- **Overclock (Overclock Technologies Limited)**: The MCP page and tool schemas give no sync interval, and results carry document and effective dates, not a last-updated or indexed time. No account found.\n- **Secoda (Secoda, Inc.)**: Nothing in the repo on sync cadence or last-updated time, and Secoda's docs were not re-read under its Terms of Use.\n\n- not this job: Alation (Alation, Inc.): Doesn't aim at recently changed company documents; no tool searches documents by change time.\n- not this job: Atlan (Atlan Pte. Ltd.): Doesn't aim at recently changed wiki, drive or chat content; knowledge files are uploaded by hand or by save_knowledge_content, which indexes them at once, and no connector catches edits, moves or replies.\n- not this job: Basedash MCP (BaseDash Inc. (Delaware, United States)): No document index; Basedash queries live data sources and has no document freshness or last-updated search.\n- not this job: ClicData MCP (ClicData SAS): No document index; the server queries data held in ClicData's warehouse, not documents.\n- not this job: Collibra (Collibra Inc.): No document index or sync of changed documents; the catalogue holds metadata assets, and no freshness or last-updated stamp on search results is documented for agents.\n- not this job: DataHub (Acryl Data, Inc. (d/b/a DataHub)): Doesn't aim at recently changed company documents; metadata comes in through ingestion runs, and documents written through the API or MCP often never appeared in search (acc-26).\n- not this job: Marmot (Marmot Data Ltd): Doesn't aim at recently changed company documents; catalogue metadata arrives through scheduled plugin pipelines, such as every six hours in the docs' examples, with a Run now button.\n- not this job: OpenMetadata (Collate, Inc.): Doesn't aim at recently changed company documents; catalogue metadata arrives through ingestion connectors, and no lag for Context Center files is published.\n- not this job: Precisely AI Studio (Precisely Incorporated): No document index or sync is described; assets operate on records and sample data.\n- not this job: Procore AI Go (Procore Technologies, Inc.): No agent interface, and the support page states no sync lag for the Procore data it answers from.\n\n## What stops agents finishing\n\n- sync runs every 1, 4 or 24 hours with no on-demand refresh\n- incremental sync misses moves and in-thread replies with no error\n- new documents written by the agent never reach search\n\n## Around it\n\nBefore: work-docs.publish. After: company-knowledge.cited-answer.\n\n## Where this comes from\n\nWeight 11 of 100 in Company knowledge \u0026 data catalogues: 4 of 38 counted accounts (Onyx Slack replies and SharePoint moves never indexed, DataHub documents not appearing, Onyx Ingestion API not seen by MCP), plus Google's connector guide naming 1 to 24 hour sync cycles\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/company-knowledge.fresh-document.json, or the MCP tool get_use_case with id company-knowledge.fresh-document. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Find a document that was added or changed recently",
        "url": ""
      }
    ],
    "description": "Find a document that was added or changed recently: 0 companies fully do it, 7 with a limit, 22 carry the tag. Every listing in Company knowledge \u0026 data catalogues with the reason and a source.",
    "facts": null,
    "h1": "Find a document that was added or changed recently",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/company-knowledge.fresh-document/",
    "published": "",
    "section": "agents",
    "title": "Find a document that was added or changed recently | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/company-knowledge.fresh-document/"
  },
  "tokens": {
    "markdown": 1700,
    "slim": 330
  },
  "version": 1
}
