Skip to Content
Agent capabilitiesLegacy Agent API

Legacy Agent API Deprecated in v26.5

The original /agent/* endpoints and kublingAgent.api configuration are deprecated. They remain documented only to identify existing integrations. Build new integrations on the native capability Task API.

Deprecated endpoints

EndpointFormer purposeReplacement
GET /agent/queryGenerate SQL from natural language.No direct replacement. Runtime actions use Logical Query v1.
POST /agent/resultsGenerate and execute SQL.Invoke a supported capability and let Kubling validate each action.
POST /agent/investigationDelegate an investigation through the legacy upstream API.POST /api/v1/capabilities/investigation/vdbs/{vdb}/versions/{version}/tasks

The deprecated endpoints use plain-text request and response shapes and depend on the legacy upstream service. They do not provide the native task envelope, server-owned action budgets, caller-filtered context or stable stop reasons.

Deprecated configuration

Existing deployments may contain:

kublingAgent: enabled: true instanceIdentifier: legacy-engine api: baseURL: https://agent.kubling.com/api/v1 statementGenerator: httpMethod: POST path: /gen/statement investigation: httpMethod: POST path: /gen/investigation keepAlive: activated: true

Do not copy this shape into a new deployment. The api block belongs to the legacy integration.

Migration

  1. Deploy a runtime compatible with Kubling’s native task protocol.
  2. Replace kublingAgent.api with connection, contextSynchronization and taskRuntime.
  3. Assign a stable instanceIdentifier and configure runtime authentication headers.
  4. Configure and validate the VDB’s semantic model when the workflow needs it.
  5. Invoke the versioned capability endpoint as a real Kubling caller.
  6. Validate caller visibility, budgets, terminal states and failure behavior.
  7. Remove clients that still call /agent/query, /agent/results or /agent/investigation.

See the configuration reference and security boundary.

No removal release is announced here. Treat the deprecation as a signal to migrate, not as permission to depend on an unspecified compatibility window.

Last updated on