> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textmine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product map

> How the current TextMine product areas fit together.

TextMine is organized around a small set of connected work surfaces.

| Area         | Use it for                                                                                                                                                    |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Workbench    | Ask questions, upload or import documents, orchestrate multi-step work, save artifacts, and work across TextMine capabilities and user-enabled MCP providers. |
| Vault        | Store documents, extract tags, review evidence, ask questions over documents, run reports, and trigger document processing.                                   |
| Legislate    | Review the validated team-document archive after documents are published from Vault into Legislate.                                                           |
| Workflows    | Build reusable automations that run manually, from document events, from email, on a schedule, or from intake forms.                                          |
| Playbooks    | Convert policies, checklists, and negotiation guidance into reusable document reviews.                                                                        |
| Records      | Turn document evidence into structured business records, schemas, relationships, graphs, and review candidates.                                               |
| Agents       | Configure on-demand AI agents that can be run directly, from Workbench, or from Workflows.                                                                    |
| Scribe       | Build and fill smart document templates with fields and conditional logic.                                                                                    |
| Integrations | Import from connected providers, submit to external systems, call APIs/webhooks, and expose TextMine's own MCP server to agent clients.                       |

## Naming guidance

Use TextMine for the overall platform. Use Legislate when you mean the publication or team-document surface: the validated data archive where documents can appear after being published from Vault.

Vault and Legislate are separate surfaces. A document can be processed in Vault, published to Legislate, and later compared across both, but a Vault search should not be described as a Legislate search unless the user is explicitly asking about published team documents.

## Agent guidance

Agents should read [For agents](/getting-started/for-agents) before acting. This Mintlify site explains product meaning and user workflows. Use [Workbench capabilities](/workbench/capabilities), [Vault and editor capabilities](/vault/capabilities), [Workflow blocks](/workflows/blocks), and [Integration catalog](/integrations/catalog) for detailed product capability maps. The developer hub at [developers.textmine.com](https://developers.textmine.com) provides Public API V3 schemas, operation IDs, ReadMe MCP, and client setup guides.

When an agent needs to execute API-backed work, it should use the developer hub [For Agents](https://developers.textmine.com/docs/for-agents) page and the [API reference](https://developers.textmine.com/reference).