Deletes an AI Tool.
Hard-deletes the tool definition; agents that still reference it by ID will fail to resolve the tool on their next invocation. If the tool ID appears in any integration's MCP `exposedToolIds` list it is the caller's responsibility to remove it via the MCP settings PATCH — stale entries are silently ignored by the MCP server but clutter the config.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration identifier.
The unique identifier of the AI Tool.
The tenant identifier
Response Body
curl -X DELETE "https://api.fruxon.com/v1/tenants/string/integrations/string/tools/string"{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Retrieves a specific AI Tool by ID.
Returns the tool definition (input schema, description, type) along with the pricing metadata used to estimate cost per invocation. The `(integration, tool)` pair is the composite key; the same `tool` ID under a different integration is a different resource.
Creates a new AI Tool.
Registers a new tool definition under the integration. The request body carries the integration ID it should belong to; the route `integration` is currently scoped for routing and logging only, so callers should ensure the two match. After creation, expose the tool to agents or MCP clients by adding its ID to the relevant allowlist.