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
| Endpoint | Former purpose | Replacement |
|---|---|---|
GET /agent/query | Generate SQL from natural language. | No direct replacement. Runtime actions use Logical Query v1. |
POST /agent/results | Generate and execute SQL. | Invoke a supported capability and let Kubling validate each action. |
POST /agent/investigation | Delegate 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: trueDo not copy this shape into a new deployment. The api block belongs to the
legacy integration.
Migration
- Deploy a runtime compatible with Kubling’s native task protocol.
- Replace
kublingAgent.apiwithconnection,contextSynchronizationandtaskRuntime. - Assign a stable
instanceIdentifierand configure runtime authentication headers. - Configure and validate the VDB’s semantic model when the workflow needs it.
- Invoke the versioned capability endpoint as a real Kubling caller.
- Validate caller visibility, budgets, terminal states and failure behavior.
- Remove clients that still call
/agent/query,/agent/resultsor/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.