Linkup vs Tavily

The boundary

After both recurring free allowances are excluded, the paid answer flips on search depth before it flips on volume. For raw fast or standard results, Linkup’s published per-call rate is lower than Tavily’s pay-as-you-go credit rate, while Tavily’s largest public monthly bundle reaches parity at roughly 100,000 basic searches. For deep search, Tavily’s advanced request consumes two credits, while Linkup prices deep search as a much larger step above its own standard request, so Tavily has the lower published deep-search unit cost. If Linkup must return a sourced answer or structured output, it adds a small output premium; Tavily’s standard Search response does not use that exact output distinction. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)

That makes the practical line explicit. Choose the standard-search comparison for latency-sensitive retrieval that returns raw results. Choose the deep-search comparison for a request that asks the provider to do broader retrieval. Do not describe a mixed month as one request count. Split standard, deep, and shaped-output calls, multiply each by its published rate, then add them. A small proportion of Linkup deep calls can dominate a much larger block of standard calls. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)

How the billing models differ

Linkup maintains a prepaid account balance and deducts a fixed amount for each successful endpoint call. Search price depends on depth and output type. Fetch depends on JavaScript rendering. Research depends on reasoning depth, and x402 payment applies the same schedule with a per-request minimum. Tavily maintains API credits through a recurring free tier, monthly bundles, or pay-as-you-go usage. Basic and advanced Search consume one or two credits, while Extract, Map, Crawl, and Research have separate success-count or dynamic credit rules. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)

Linkup explicitly says errors, missing parameters, internal failures, and responses with no relevant result do not deduct credit. Tavily explicitly exempts failed Extract and Map calls, but the reviewed credit page does not extend that promise to Search. The page therefore does not assume identical failure billing for Search. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)

What each offers that the other does not

Linkup publishes raw results, sourced answers, and structured outputs as explicit Search output types, an x402 payment option without a normal account, separate Fetch and Research endpoints, and task billing that mirrors direct calls. Tavily publishes site Map and Crawl operations, success-counted multi-URL Extract, and a Research operation with bounded dynamic credit use. Linkup is the direct fit when response shaping or per-call on-chain settlement is part of the requirement. Tavily is the direct fit when mapping and crawling a site belongs in the same API. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)

Who should pick which

Pick Linkup for mostly standard raw-result calls below the point where Tavily’s largest bundle reaches unit parity, especially if no-result calls are common or a shaped answer is worth its disclosed premium. Pick Tavily when advanced search is a material share of traffic, when the 100,000-credit bundle will be fully used, or when Map, Crawl, and Extract replace separate systems. For a mixed workload, the switching condition is the percentage of deep and shaped-output calls, not total searches alone. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)

Linkup does not publish whether paid prepaid credit expires, and Tavily does not clearly publish Search failure billing or paid-credit rollover in the reviewed guide. Those omissions can matter more than a small unit-rate difference for intermittent use. (Linkup pricing documentation, retrieved 2026-07-26; Tavily credit documentation, retrieved 2026-07-26)