Integrations · Tavily
Guild agents use Tavily to search the web, extract page content, crawl sites, and run multi-source research without leaving your platform. Guild stores the Tavily API key server-side and injects it through the credential proxy, so agent code never sees the secret. Credential policies let you restrict which Tavily operations each agent or workspace can call.
Book a demo
See how teams govern agents that use Tavily.
Talk to sales
Get access to Guild, then connect Tavily to your first agent.
What the Tavily integration exposes
The integration provides tools that cover web search, URL content extraction (single URL or batches of up to 20), graph-based site crawling, site mapping, and multi-source research that runs searches, analyzes sources, and returns a report. Tools for retrieving research task status, checking account usage, pulling per-request logs, and submitting result feedback are also included.How it works
1
Open credentials settings
In Guild, go to Access & setup > Credentials. The page lists connected credentials and shows a gallery of available integrations.
2
Connect the Tavily API key
Click Connect, select tavily-openapi, and paste your Tavily API key into the API Key field. Guild sends the key as a bearer token in the Authorization header on every request.
3
Import tools into your agent
Import TavilyOpenapiTools from the integration package and spread it into your agent’s tools object. Use pick() to include only the specific tools your agent needs.
Why Tavily access needs governing
Tavily credentials give an agent the ability to search the web, extract content from arbitrary URLs, crawl sites, and retrieve account-level usage and billing data. Guild stores the API key server-side and injects it through the credential proxy, so the key never enters agent code, containers, prompts, or state. See Security architecture for how the proxy works. Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request reaches Tavily. You can restrict specific operations, scope rules to individual agents or workspaces, and block mutating calls while permitting read operations. Scoping a credential to one workspace, one member, or one agent limits blast radius if something goes wrong. Without scoped rules the credential starts with an allow-all policy; delete that default once your rules cover everything agents should reach. See Credential policies and Credentials.About the Tavily integration
This integration connects Guild agents to the Tavily REST API for web intelligence tasks. Agents can search the web, extract content from URLs, crawl and map websites, and conduct comprehensive multi-source research. Account and usage management tools are also available. The integration isguildai~tavily-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Tavily
In Guild, go to Access & setup > Credentials, click Connect, select tavily-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thetavily_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~tavily-openapi:
Frequently asked questions
Can I limit which Tavily operations a specific agent can call?
Can I limit which Tavily operations a specific agent can call?
Yes. Credential policies support ALLOW and DENY rules scoped to individual agents. You can permit operations like tavily_openapi_search and tavily_openapi_extract while denying tavily_openapi_post_org_usage for agents that have no reason to read billing data. See Credential policies.
Does the agent code ever see the Tavily API key?
Does the agent code ever see the Tavily API key?
No. Guild’s credential proxy injects the key as a bearer token in the Authorization header server-side, after the policy check passes. The key never enters the agent’s code, container, prompt, or state.
Can I use a different Tavily account in one workspace than the rest of my organization uses?
Can I use a different Tavily account in one workspace than the rest of my organization uses?
Yes. Connect a workspace-scoped credential from the workspace’s Credentials page and choose The whole workspace. Guild will use that credential for agents in that workspace ahead of the organization-wide default. See Credentials.
Does Tavily send webhook events to Guild?
Does Tavily send webhook events to Guild?
Not yet. The catalog entry for guildai~tavily-openapi lists no webhook events, so event-driven triggers from Tavily are not available through this integration.
Put a governed agent on Tavily this week
Book a demo
See how teams govern agents that use Tavily.
Talk to sales
Get access to Guild, then connect Tavily to your first agent.