API console App botyard.io Overview Getting Started Provider credentials Runtime Vault GitHub integrations Workforces Exfiltration scanning

API authentication Generating API clients API reference

Bot model settings

Bot tool domain settings

Device enrollment

Integration logins

Integrations economic

Integrations github

Integrations oauth

Integrations vending

Managed credits

Mcp catalog public

Notification preferences

Outbound emails

Per user claude

Push registrations

Secret policies

List Servable Tools List Tools Get Tool

Vault input requests

Workforce task files

MCP setup templates Manage Botyard with Terraform

API

Tools

Botyard REST API endpoints for tools.

3 endpoints in this group. Every request authenticates with an API key; see the API reference for the other groups.

List Servable Tools: GET /v1/orgs/{org_id}/tools/servable
List Tools: GET /v1/orgs/{org_id}/tools
Get Tool: GET /v1/orgs/{org_id}/tools/{tool_id}

Set Opt Out

Set the bot's global suggestions opt-out flag. Returns the resulting suggestion surface (empty when opting out). Pure metadata write — no config change or reconcile.

List Servable Tools

List visible tools annotated with servability for a hosting profile. Pre-creation companion to the plain catalog listing: the creation wizard knows its ``(hosting_type, harness)`` profile but has no bot row yet. Every visible row is returned; servable rows carry a null reason and the rest explain why the profile cannot serve them, so a picker can offer the former while showing the latter disabled with a reason. Scoped to the MCP servers the caller can see: tools from a private server are absent, not disabled-with-a-reason. "Servable" is a runtime fact the picker is entitled to explain; "you may not see this server" is not.