AIP
Connect business tools
Let Agents call HTTP services with explicit inputs and authentication.
Choose a tool type
| Configuration | Use case |
|---|---|
| Dynamic HTTP tool | Expose a business operation with a defined name, inputs, and result |
| Event tool | Emit tool events to an existing integration and configure a response template |
| HTTP proxy | Set allowed hosts and injected request headers |
Configure a dynamic HTTP tool
For order lookup, first prepare a business endpoint that accepts requests and returns JSON.
- Open business tools in the Agent editor and add an HTTP tool.
- Name it
lookup_orderand describe it as “Look up the current status by order number.” - Enter the business service URL.
- Add an input schema with a required string
order_id. - Reference a bound secret in headers if authentication is required.
- Apply the tool configuration, then save the Agent.
{
"type": "object",
"properties": {
"order_id": {"type": "string", "description": "Order number supplied by the customer"}
},
"required": ["order_id"],
"additionalProperties": false
}In debugging, ask “Check the status of order DEMO-001.” Replace the example with your test data. Check the selected tool, complete arguments, and whether its response is sufficient to answer.
Configure an HTTP proxy
Set host rules and headers for the business requirement. Reference secrets instead of pasting real tokens into prompts. Verify host scope so one system's authentication headers are not sent elsewhere.
When calls fail
Inspect the debug tool error, then check the URL, input schema, headers, and secret bindings. Apply in the tool dialog only updates the draft; save the Agent afterward.
Event tools require a corresponding event-processing service. A response template does not perform the actual business operation.