Skip to content

Explore Seny

Tools

Documentation

Tools

Tools are what let the agent do things— not just answer questions. Every Seny agent comes with a built-in set of tools for reading and driving the page it's on, searching your content, and remembering visitors. You can also define custom tools that call your own backend.

Built-in tools

Built-in tools are always available — there's nothing to enable. The full list is shown read-only under the agent's Permissions tab. (The old Tools tab was renamed: custom and third-party tools now live under Integrations.)

Seeing & driving the page

The browser tools act on the live page the visitor is looking at. The agent first calls observe_page to take a snapshot of the current DOM — visible text, forms, buttons, links — and then acts on what it saw. Nothing here depends on the crawl; if the page changes, the next snapshot sees the change.

Reading & searching content

Memory & context

Voice sessions (phone and web voice)

These are voice-session tools — they run on phone calls and on web voice sessions alike, not phone-only.

Custom tools

Define your own tools to connect the agent to your backend. Good examples: check inventory, book an appointment, look up an order, create a quote, send a notification to Slack. Add them from the agent's Integrations tab.

The HTTP tool

The most flexible option: you define the entire request and Seny fires it when the agent calls the tool.

The request runs with a 15-second timeout and no automatic retry. Whatever your endpoint returns is handed to the agent as the response status plus the body — parsed JSON when possible, otherwise text, truncated to 4,000 characters — and the agent speaks from it. Keep responses small and relevant; the agent does better with "4 racks available after 3pm" than with a full database row.

The webhook tool

A simpler fire-and-forget variant: give it a URL and Seny POSTs a fixed JSON body when the agent invokes it —

{
  "message": "what the agent wants to tell your system",
  "context": { ... },  // optional structured context, passed through
  "conversationTime": "2026-05-01T19:46:12.000Z"
}

with a 10-second timeout. Use it for notifications ("ping Slack when someone asks for a demo") rather than lookups.

Authentication

Seny does not sign custom tool calls. Authenticate them the way you'd authenticate any client: put an API key or bearer token in the headers you configure on the tool, and check it on your side. Secrets you enter are stored encrypted and substituted into the request at call time.

Tool call timing

HTTP tools time out after 15 seconds and webhook tools after 10; there is no automatic retry. While a tool runs the agent keeps the visitor engaged, but slow endpoints make slow conversations — keep them fast.

Talk to Seny