Tavily MCP integration

They can. Tavily Search is documented at roughly two requests per second and returns HTTP 429 on bursts, with exponential backoff as the expected response. A conversation that needs several searches should space them rather than firing them at once.

They are metered separately. Get Tavily Usage reports credit consumption, limits, and per-endpoint usage across search, extract, crawl, map, and research, so you can see which operation is consuming the budget rather than only the total.

Tavily Search returns a 401 when the connection is not active. Lyro surfaces that as a retrieval failure instead of answering from nothing, and hands the conversation to a human agent with the history attached if the customer still needs the answer.

Yes. Tavily Search supports domain filtering alongside search depth, content type, and result count, and Tavily Crawl adds its own domain filtering with depth and breadth limits, so retrieval can be pinned to your own site and a short list of approved sources.