API Request: Models, Agents, Plugins & Knowledge Base

1. Model Configuration & API Key Management

We require the ability to manage model configurations and rotate API keys programmatically to meet security and compliance standards (e.g., ISO 27001).

Currently, API v1.2.0 does not support model or API key management.

Requested endpoints:

• GET /v2/models – List configured models

• POST /v2/models – Add new model configuration

• PATCH /v2/models/{id} – Update model details (e.g., rotate API keys)

• DELETE /v2/models/{id} – Remove model configuration

Business justification:
Automated API key rotation is critical for enterprise security compliance. Manual configuration creates operational risk and does not scale.

2. Agent Creation & Management

Currently, the API only provides read-only access (GET /v1/ai-characters), which limits automation.

Requested endpoints:

• POST /v2/agents – Create new agent

• PATCH /v2/agents/{id} – Update agent configuration (system prompt, model, access control, etc.)

• DELETE /v2/agents/{id} – Remove agent

Business justification:
This capability is required to support Agent-as-a-Service workflows, allowing us to deploy and manage agents automatically through CI/CD pipelines without manual Admin Panel interaction.

3. Plugin Installation & Configuration

We need to standardize plugin deployment across multiple TypingMind instances to ensure consistent functionality.

Requested endpoints:

• GET /v2/plugins – List installed plugins

• POST /v2/plugins – Install and configure plugins

• PATCH /v2/plugins/{id} – Update plugin settings

• DELETE /v2/plugins/{id} – Remove plugins

Business justification:
Lack of programmatic plugin management prevents Infrastructure-as-Code workflows, introduces configuration drift, and increases operational overhead.

4. Knowledge Base Management

Currently, uploading and managing knowledge documents is a manual process.

Requested endpoints:

• GET /v2/knowledge – List knowledge bases and documents

• POST /v2/knowledge – Upload documents and create knowledge base collections

• DELETE /v2/knowledge/{id} – Remove documents or collections

Business justification:
Automated knowledge ingestion is essential for scalable enterprise onboarding. Manual uploads do not scale for high-volume or multi-tenant deployments.