WorkerKit

AI workers for Tavily

Ready-made AI workers that research with Tavily: questions answered from live sources, with the pages they relied on named, so the finding can be checked rather than trusted.

What is an AI worker for Tavily?

An AI worker using Tavily is an AI agent that can look things up on the live web as part of its job, through a search connection built for exactly that. It is rarely the whole job. The pattern is a worker that already has work to do, and needs the current state of the world before it can finish, such as checking whether a company still exists before writing to them.

What these workers do

Enrich a new lead before filing it

Looks up what a company publicly does and how big it is, so the record lands with context rather than as a bare email address.

Check a claim before it ships

Verifies the facts in a draft against current sources and flags what could not be confirmed instead of letting it pass.

Track what a competitor announced

Reads for public changes on a schedule and reports what is new, with the announcement itself cited.

Brief you before a first meeting

Assembles what is publicly known about a company and the people you are meeting into a short read, sourced throughout.

How an AI worker runs in Tavily

Search as an ingredient, not the product

Findings carry their sources

Where it is worth reaching for

Tavily questions, answered.

Does a research worker browse the entire web?

It issues searches and reads what comes back, in the same way a person opening a few tabs does. It is not crawling the web or holding a copy of it, and each run looks up only what the job in front of it requires.

Can I tell whether a finding is trustworthy?

Yes, because the sources come back with the finding. Workers here are written to name what they relied on, so you can follow a claim to the page it came from rather than deciding whether to believe a paragraph.

Does searching expose my own data?

A search sends the query, not your systems. What goes out is the question the worker needed to ask, and you control what a worker may read internally, so a research step does not become a route out for private records.

Should a worker use search for questions about my own business?

No, and the well written ones do not. Your own connected systems are authoritative about your customers, deals, and documents, and the public web is not. Search belongs to the parts of the world your systems have no record of, which is why a kit that reaches for it to answer an internal question is a kit worth questioning.

What AI workers can do in Tavily

The tools a worker can be granted in Tavily once you connect it. A kit grants only the ones its job needs, and you can narrow them further on the worker.

Tavily Web Search

Search the public web with Tavily and get ranked results (title, url, snippet, and — where visible — content, score, published date, author, source). Set `includeContent` to pull page text inline where supported. Read the `accessInfo` field: results are filtered by the connection's egress (domain/URL allow-block) rules, so a short list may be scoped rather than exhaustive.

Tavily News Search

Search recent news across the public web with Tavily, returning ranked news results (same result shape as tavily_search). Pass `days` to pin the window for dated questions (e.g. days=1 for yesterday's news) — without it Tavily applies its default news window (3 days), not the one you asked about. Read `accessInfo` for any egress filtering applied.

Tavily Read Page Contents

Fetch clean, readable page text for one or more URLs with Tavily (e.g. to read a page from tavily_search). Each URL is checked against the connection's egress rules before fetching; blocked URLs are dropped and summarised in `accessInfo`.

Tavily Answer

Ask Tavily a question and get a synthesized answer with citations, returned in `answer` alongside the supporting `results`. Cited sources are subject to the connection's egress rules — read `accessInfo` for any filtering.

Browse Tavily kits

All apps