AckdbAgentWebSearchStatus

Effective web access for the agent. Trust `active`, not `enabled`: a deployment can have web access turned on while running a provider that cannot honor it, in which case /ask stays offline and `inactiveReason` says why. anthropic enforces maxUses + allow/block lists; openai enforces an allow-list only (no block-list, no cap); kimi/glm cannot search.

Properties

enabledboolean

Web access is turned on for this deployment.

activeboolean

enabled AND the current provider supports it - the next /ask really can search.

supportedboolean

The current provider can run a server-side web search.

inactiveReasonstring (nullable)

Why enabled web access is not active - unsupported provider, a custom openai baseUrl, or a domain list the provider cannot enforce (web access fails CLOSED rather than searching unrestricted). null when active or simply disabled.

unhonoredSettingsarray of

Budget-hint settings this provider silently cannot apply while search still runs (e.g. maxUses on openai). Boundary settings never appear here - they deactivate instead.

string

sourcestring

custom = stored via PUT /config/agent; default = AGENT_WEB_SEARCH env defaults.

"custom""default"

maxUsesinteger (nullable)

Configured cap on searches per MODEL REQUEST (one /ask makes several). null = the default of 5 is sent. Enforced on anthropic only.

allowedDomainsarray of

Results limited to these hosts.

string

blockedDomainsarray of

Results never from these hosts.

string

Example

AckdbAgentWebSearchStatus example

{
  "enabled": false,
  "active": false,
  "supported": false,
  "inactiveReason": "string",
  "unhonoredSettings": [
    "string"
  ],
  "source": "custom",
  "maxUses": 0,
  "allowedDomains": [
    "string"
  ],
  "blockedDomains": [
    "string"
  ]
}