Can the model set arbitrary headers or query parameters?
Only when the tool allows it. Runtime-supplied headers, query parameters and JSON bodies are off unless the tool config enables them, and unsafe headers are blocked.
Most integrations are an HTTP request with the right credential. AgentRow's HTTP API tool describes that request once, with templates the model fills from a JSON Schema, and turns it into a capability the agent can call under limits you set.
Read-only lookups against internal services: order status, account details, inventory, ticket state.
Actions behind approval: create a ticket, schedule a callback, update a record.
Chains of calls where the model uses one result to fill the next request, all visible in the trace.
The shape a tool takes in the AgentRow builder API. Credentials are stored on the tool's auth settings, not in its configuration, so they never reach a prompt. Placeholders in double braces are filled by the model from the input schema.
{
"name": "get_order_status",
"type": "http_api",
"description": "Look up an order by id and return its status, items and delivery estimate. Use when the user asks about an order.",
"auth_type": "api_key",
"safety_level": "safe_read",
"is_readonly": true,
"timeout_ms": 8000,
"config": {
"method": "GET",
"url": "https://api.example.com/v1/orders/{{order_id}}",
"query_params": { "expand": "items" },
"allowed_domains": ["api.example.com"],
"expected_status_codes": [200, 404]
},
"input_schema": {
"type": "object",
"properties": {
"order_id": { "type": "string", "description": "The order id, for example ORD-10422" }
},
"required": ["order_id"]
}
}Every call appears in the run trace with the rendered request, the response status and body, timing, retries and errors, plus what the model was shown of the result. If the model never called the tool, the toolbox step shows whether it was bound for that model call and why.
Only when the tool allows it. Runtime-supplied headers, query parameters and JSON bodies are off unless the tool config enables them, and unsafe headers are blocked.
The model receives a preview plus a handle; the full response is stored and can be read in parts with the built-in tool_history tool. Responses are also capped by a maximum size.
Yes. With the end user token auth type the signed-in end user's own token is forwarded as the credential, and the tool binds only when a run has a signed-in user.
Connect AI agents to HTTP APIs, webhooks, web pages and other agents with typed tools: JSON schemas, auth types, safety levels, limits and call logs.
Tool types, what a tool defines, how results reach the model, tool selection with search_tools, and authenticated tools for signed-in users.
Compare AgentRow and LangFlow for AI agents: visual workflows, multi-agent orchestration, RAG, observability and what it takes to run in production.
Slack, HubSpot, Stripe, Shopify, GitHub, calendar, email, wikis, webhooks and any REST API.
Join the waitlist for early access. Tell us which systems you need to connect and we will point you at the right tool definitions.