Tavily through Squiid

What Tavily is

Tavily is a search API whose output is shaped for a model rather than for a person. A single request performs the search, fetches the pages, strips navigation and boilerplate, and returns ranked snippets with URLs, optionally including a short synthesised answer and raw page content. Parameters control search depth, topic, recency, and which domains to include or exclude, and there are extract and crawl endpoints for pulling content from specific URLs once you have found them. Results carry a relevance score, so a pipeline can drop weak matches before they take up space in a context window.

This removes a step agents are bad at. Without it, an agent searches, gets a list of links, fetches each one, wrestles with markup and cookie banners, and burns a lot of tokens on navigation text before it reaches the paragraph that mattered. Research assistants, competitor monitoring, due diligence tools, fact checking and any chat feature that must know about last week all use it the same way: search, take the context, put it in the prompt. It also behaves predictably in a tool definition, which matters when the model decides how many searches a question deserves.

Why connect it through Squiid

Because agents search in loops, the cost is per call and easy to lose track of. Squiid meters Tavily against prepaid credits at the provider's list price and shows searches per day, so a runaway research loop is visible immediately. Requests go to https://api.squiid.io/v1/tavily/... with Authorization: Bearer $SQUIID_API_KEY, the official clients work by pointing their base URL at the gateway (gateway convention), and the spend lands on one monthly invoice next to the model tokens it produced.

• One account, one key, one bill, one dashboard. Tavily sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Tavily credentials. Your code carries SQUIID_API_KEY, so TAVILY_API_KEY, TAVILY_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Tavily costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Agent-ready search results with cleaned content
• Optional synthesised answer in the same call
• Domain, topic and recency filters
• Extract and crawl endpoints for specific URLs
• Tavily list pricing, no markup

How to connect Tavily

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces TAVILY_API_KEY, TAVILY_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/tavily/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Tavily charges credits per search, with deeper searches costing more, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Tavily usage, with no markup and no per-request margin.

Tavily has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Tavily usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Tavily is usage-metered, so leaving means creating your own Tavily key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Tavily's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Tavily through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Tavily usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.