Skip to main content
POST
List target tool catalog

Restrictions

Usage

  • Use target_locator to identify the target; target_kind is optional and is inferred from current target routing when omitted.
  • If multiple kinds match the same locator, the response is HTTP 200 with data.error.code = "ambiguous_target_kind" and a target_kinds list — retry with an explicit target_kind.
  • The catalog is a candidate capability view, not an execution guarantee. The target Agent may go offline between catalog and invoke, or local Agent policy may block individual tools at invoke time.
  • Each tool entry exposes only name, target_kind, description, and input_schema. It does not expose tool versions, output contracts, catalog revisions, or execution limits.
  • Business errors (target_unavailable, timeout, forward_failed, invalid_tool_result, ambiguous_target_kind) return HTTP 200 with data.error present and data.tools = []. Only protocol, authentication, and internal errors use the standard error envelope.
  • The response uses sparse fields: on success error is omitted rather than sent as null, and target is omitted when the locator could not be uniquely resolved. tools is always present.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json
target_locator
string
required

Target identifier (host name, MySQL address, …). Max 256 bytes; no whitespace, control characters, or |.

account_id
integer<int64>

Optional consistency check. Must equal the authenticated account when supplied.

target_kind
string

Optional target kind. When omitted, webapi infers it from current target routing. If the call returns ambiguous_target_kind, retry with a value from target_kinds.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Endpoint-specific payload. See each operation's 200 response schema.