We have refreshed the TextMine developer hub around Public API v3, agent-friendly docs, and MCP.

Public API v3 is now the default

The default developer reference now points to V3 Public API. New integrations should use v3 unless they have a specific legacy dependency on v2.

The v3 OpenAPI reference now covers the current public API areas, including:

Vaults, documents, search, document types, metadata, tags, assignees, and users.
Integrations for provider discovery, provider folder/file browsing, and provider imports.
Workflows, workflow triggers, workflow conditions, and workflow actions.
Agents, reports, alerts, exports, business records, and API keys.

Start here:

MCP quickstart added

We added an MCP quickstart for Codex, Claude, and other MCP-compatible clients:

MCP Quickstart
ReadMe MCP URL for developer docs and API-reference tools: https://developers.textmine.com/mcp
Central TextMine MCP URL for product tools: https://mcp.textmine.com/mcp
Agent-friendly index: llms.txt

Product MCP clients should call the central TextMine MCP endpoint and pass the caller's own TextMine bearer key when they need to execute authenticated API calls. Agents should prefer discovery operations such as listVaults, listIntegrationProviders, and workflow catalog endpoints before mutating data.

If a client cannot initialize against the ReadMe MCP URL, confirm that the ReadMe MCP switch is enabled in the project dashboard. If it cannot initialize against the central TextMine MCP URL, confirm the client is using Streamable HTTP and a valid tm_... key.

Guides refreshed

The Guides section is now visible and has been updated with current TextMine product language:

Core Concepts explains Vault, Legislate, Workbench, Workflows, Playbooks, Records, Agents, Scribe, and Integrations.
Document Ingestion covers both direct uploads and provider imports.
Legislate Archive clarifies that Legislate remains the validated archive for documents published from Vault.
Reports, Workflows, and Agents explains how document intelligence becomes repeatable automation.

We also removed the stale generated TextMine Public Api reference category so the reference is cleaner and points users toward the v3 OpenAPI reference.

For broader product context

Use docs.textmine.com for user-facing product guidance and this developer hub for endpoint-level reference, MCP, and integration work.

Changelog

Public API v3 and MCP documentation updates

Welcome to Vault