Website tools
Turn a business's own website into lookup tools the agent can call during a call, without writing an endpoint or holding an API.
Most businesses already publish the facts a caller asks about: products and prices, opening hours and locations, policies, FAQs. A website tool reads that site during a call so the agent can answer from it without an API.
Connect the site once and describe what the agent should look up. Vertical AI builds a matching tool and adds it to the agent.
Website tool or webhook tool
Reach for a website tool when the facts are public, already on the site, and you have no API to point at. It tracks the site as the site changes.
Reach for a webhook tool when the agent needs private data, needs to write to your system, or when the answer must be exactly right every time.
Both coexist on the same agent. A common shape is website tools for the catalogue and opening hours, plus a webhook tool for the one lookup that hits your own system.
Connecting a website
- Open the agent's Tools page and choose Add tool, then Website.
- Enter the site's address and describe the lookup you want, for example "search the store for products the caller names" or "answer questions about opening hours".
- Vertical AI reads the site and builds a lookup that does what you described. This can take a few minutes.
You get the one tool you described. To add another lookup, describe it the same way.
Connecting a new site is restricted to workspace owners because it mints a credential and makes outbound requests. It is also limited to 10 new sites per workspace an hour.
Adding another tool to an already-connected site needs no reconnect. Describe the new lookup and it reuses a matching one or extends the site's lookups. The Tools page groups every tool under the site it came from.
What gets added
A website tool is an ordinary tool on the agent. It calls an endpoint Vertical AI hosts for that site, authenticated by a key held as a secret variable:
POST https://app.verticalai.com.au/api/site-api/lookup/{{lookup_id__acme}}/search_products
X-API-Key: {{lookup_token__acme}}The two variables are named after the site, here acme.com.au. The id is a plain
variable and the token a secret one, so each connected site has its own pair.
You can sharpen its description, mark it background-safe, and give it prerequisites. It lands in a draft and reaches callers only when you publish.
The endpoint only fetches the address you connected. There is no way for a caller, or the model, to make it fetch something else.
What the agent sees
Each time the agent calls the tool, the endpoint checks the key, runs the lookup against the site and hands back what it found.
When a lookup finds nothing, or fails, the agent recovers in the conversation, the same as any other tool. See tool errors are instructions.
Limits
- Requests per minute are capped at 120 for each connected site. That's generous for real conversations, and a ceiling on a runaway loop.
- Some sites cannot be read. A site behind an aggressive bot wall, or one that publishes nothing readable, may fail to connect or give thin answers. A failed connection is reported, and a webhook tool is the answer for that business.
- Read-only. Booking, ordering, and anything that changes state belongs in a webhook tool or a connected app.