Models and Operators

Models configure the model services used by workflows, knowledge bases, and related features. Custom operators encapsulate reusable data-processing logic. The two resource types have different creation entry points and management flows.

Manage models

Create a model resource

  1. Open Resource Center > Models.

  2. On the type tabs provided on the page, select the target type, such as LLM Model or Document Parsing. Whether other tabs appear depends on the current page.

  3. Click New Model.

  4. Fill in the fields for the selected type, such as model resource name, interface protocol or backend type, API endpoint, API key, timeout, and model list.

  5. When the page offers Fetch Model List, enter the API endpoint and API key first, then run the fetch. The result only populates the model options in the current form.

  6. Click Confirm, then verify the result in the model resource list.

Form fields differ by type. Document-parsing resources may require a parser type, supported MIME types, or a service address. Follow the fields and validation messages shown on the current tab.

View and filter models

The model resource list supports search by name, type, or model, and filtering by the types provided on the page. The list shows name, type or interface protocol, model list, timeout, number of API endpoints, creation time, update time, and actions.

Judge whether a model resource was created from the list contents only after the list has finished loading. A success message in the creation dialog only means the create request returned successfully.

Edit, delete, and manage models

List actions depend on your current permissions and the resource type:

  • Edit: Modify the model resource configuration.

  • Delete: Delete the model resource after a second confirmation.

  • Manage API Endpoints: View, add, or update model service addresses.

  • Update API Key: Update the API key for an existing model resource.

Before deleting, confirm that workflows, knowledge bases, or other pages are no longer using the model resource. Treat list refresh and page messages as the source of truth for the delete result.

Manage custom operators

Create an operator

  1. Open Resource Center > Catalog and open the target database details.

  2. Click Create > Operator.

  3. Select an operator type provided on the page, then fill in name, identifier, version, and description.

  4. Configure code, SQL, or base-node binding for the selected type. When input/output fields or mappings are required, use the field configuration provided on the page.

  5. Click Save.

When the code or SQL configuration page provides a test entry, complete the test before saving the version. If the test fails, use the page error message to check the code, SQL, and input mapping.

Manage operator versions

The custom operator list shows name, identifier, language, type, version, version count, status, and update time. Available actions depend on permissions and the current version status:

  • View or Latest Version: Open operator details.

  • Edit: Modify the current version.

  • New Version: Create a new version from an existing operator.

  • Enable or Disable: Change the current version status.

  • Delete: Delete the specified version after confirmation.

Before deleting a version, confirm that workflows or agents do not depend on it. When changing logic, prefer creating a new version, then enable the appropriate version according to the page status.

Publish an operator API service

When operator version details provide API service entry points, you can publish, enable, disable, or republish the service with the buttons on the page. The page may show service status, service name, authentication method, call endpoint, call examples, and an online trial entry.

This page describes only the visible entry points and configuration scope. It does not expand page fields into a fixed API protocol, authentication rules, rate limits, or billing commitments. Callers should follow the call endpoint, parameter descriptions, and examples shown on the API service page.

Read-only objects

System objects and subscribed objects may not provide create, edit, enable, disable, or delete actions. When the page shows a read-only notice, you cannot modify the object from this page.

Last updated on