All products / Tavily

Tavily pricing

How Tavily meters basic and advanced search, what remains open, and which AI-search workloads fit.

BoundedPrice recorded on 2026-09-02Rechecked Sep 2, 20262 vendor sourcesSee the calculation
Available volumes
Depth and variants

one default result set; no fan-out

Fixed for this page; volume is the control.

Every available option was priced in advance from published vendor rules. Changing a control only switches between those checked options; nothing is sent anywhere and no account is needed.

Your job

Workload100,000 search calls
Depth and variantsone default result set; no fan-out
Bills failed fetchesnot published
per 1,000 searchesnot computable for this state

What Tavily counts

1standard searches: 1 credit per request
2Project has an unpublished base price plus at least $768.00 of published overage; the total remains unknown

What you pay

At least $768.00BoundedPart of this bill is published; the total is not.ProjectProject price is not published, so its total is unknownCheck Tavily's official pricing
  1. Successes you want

    100,000 standard searches

    Your stated workload. Every vendor on this site is priced against this same number.

  2. ÷ 1

    Attempts you are billed for

    100,000 standard searches

    Tavily bills failed fetches. This workload assumes none fail, so nothing is added here.

  3. Cash per month

    At least $768.00

    Project price is not published, so its total is unknown

Bars share one linear scale across the 2 counted stages, so a multiplier shows as length. Units differ by stage and are labelled. Cash is not on that scale.

At least $768.00 missing base or overage figure total remains unknown

What could and could not be computed
  1. standard searches: 1 credit per requestsource
  2. consumes 100,000 credit per month
  3. Project has an unpublished base price plus at least $768.00 of published overage; the total remains unknownsource

Bounded. Part of this bill is published; the total is not.

Project price is not published, so its total is unknown

This is a finding about what Tavily publishes, not a gap in the data. It stays visible so a definitive market claim cannot quietly ignore it.

Published exact bills for comparable products

Same 100,000 standard search calls with one default-depth result set per call, ranked by what you would actually be billed. Unknown totals never enter the numeric order. Showing 6 of 17.

Every Tavily plan

Published plans, with the offer this workload actually selects marked
PlanMonthlyIf billed yearlyPrepaid packIncludedSimultaneous sessions
Pay as you goNot publishedn/an/an/an/a
ProjectNot publishedn/an/a4,000 creditn/a

What consumes a unit

This is where a bill actually grows. One operation is not one billed unit, and the multiplier is published here rather than on the pricing page.

Every published way Tavily charges
OperationCostsPerSource
search.query1 creditrequestsource
search.deep2 creditrequestsource

What Tavily does not publish

What Tavily is

Tavily is a search API built for applications and AI agents that need web results as input to retrieval, research, and answer-generation workflows. Its public API family also documents extract and map operations, but the recorded product meter here is centered on search. Exa, Brave Search API, and Perplexity’s developer search products are its three nearest named competitors. Tavily differs in the reviewed pricing material by making the search-depth choice itself the main multiplier: basic and advanced searches draw different amounts from one credit balance. Sources: Tavily, Tavily API credits, Exa, Brave Search API, and Perplexity, retrieved 2026-07-26.

How billing works

One unit is a credit. A basic search request consumes one credit, while an advanced search request consumes two. These are replacement rates based on the selected search depth, not two charges stacked on the same call. The ongoing free plan renews its search-credit allowance monthly, and paid plans publish an overage path per credit. The buyer mistake to avoid is counting API calls without preserving search depth. Two applications can issue the same number of calls but consume different credit totals if one defaults to advanced search. Source: Tavily API credits, retrieved 2026-07-26.

The pricing guide explicitly says failed Extract and Map calls are not billed, but it does not make the same statement for Search. Tavily’s FAQ advertises zero data retention, which is relevant to teams sending sensitive query context, but downstream storage and redistribution permissions remain separate procurement questions. Sources: Tavily API credits and Tavily FAQ, retrieved 2026-07-26.

What Tavily does not publish clearly

  • Whether a failed Search request consumes credits. Source reviewed: Tavily API credits, retrieved 2026-07-26.
  • Whether unused monthly credits roll into the next billing period. Source reviewed: Tavily API credits, retrieved 2026-07-26.
  • A complete customer-side rule for caching, redistribution, and attribution of returned content. Sources reviewed: Tavily API credits and Tavily FAQ, retrieved 2026-07-26.
  • A clean resolution of an older tutorial reference to a fractional-credit search mode against the current pricing guide’s one-credit grouping. Source reviewed: Tavily API credits, retrieved 2026-07-26.

Who it suits

Tavily suits agent and retrieval teams that can label each request basic or advanced and budget directly from that mix. It is less suitable when procurement requires explicit Search failure treatment, rollover, and redistribution terms without a support exchange. The reason is that the primary search multiplier is clear, while several contract edges around unsuccessful calls and downstream use are not answered on the reviewed public pages. Sources: Tavily API credits and Tavily FAQ, retrieved 2026-07-26.

Answer

Tavily starts at $768.00 for 100,000 searches, but the total is unknown because a required billing rate is not published.

Recorded 2026-09-02 from the vendor's own pricing page.This published price is inside the 30-day comparison window. Confirm it on the vendor's pricing page before buying.