Home
TextMine Developer Hub
Build with TextMine Public API V3, connect agent clients through MCP, and provision autonomous third-party agent workspaces with service-account API keys.
Start here
| Goal | Start with |
|---|---|
| Call Public API V3 directly | API Reference and Public API Quickstart |
| Let an MCP client inspect docs and schemas | ReadMe MCP at https://developers.textmine.com/mcp |
| Operate TextMine through the hosted product MCP surface | TextMine MCP at https://app.textmine.com/mcp |
| Provision a multitenant third-party agent organization | Agent self-service signup |
| Understand agent-safe operating patterns | For Agents |
Agent and MCP entry points
- Agent guide: https://developers.textmine.com/docs/for-agents
- MCP quickstart: https://developers.textmine.com/docs/textmine-mcp
- Agent self-service signup: https://developers.textmine.com/docs/agent-self-service-signup
- Agent index: https://developers.textmine.com/llms.txt
- Full context pack: https://developers.textmine.com/page/llms-full
API keys
Public API V3 uses TextMine bearer API keys. Existing customers can create or request keys through the access flow available for their organization. Autonomous third-party agents in the multitenant, non-enterprise deployment can use Agent self-service signup to create a dedicated organization and encrypted service-account API key.
Store tm_... keys in a trusted runtime or secret manager. Do not put raw keys into prompts, task transcripts, chat messages, or model-visible context.