fshy

fshy / Crawling

Tavily keyless

tavily.com · Crawling · 2 records · JSON

Tavily Crawling

caveatemailno cardDrequest-rate

www.tavily.com/pricing · search API · crawler-scraper/tavily · JSON · compare

Free tier1,000 API credits a month, no credit card, reset on the first of the month
unit requests; metered on request-count
Pricenone stated
Per-object capnot applicable: the unit is a request
Retentioncredits reset monthly and do not carry over
Egressnot applicable: JSON answers
Identityemail no credit card stated
Limits
  • request-rate 1,000 credits a month; requests stop when they are spent until the reset or an upgrade source
  • request-rate USD 0.008 per credit pay-as-you-go; Project plan USD 30 a month source
Bindingrequest-rate
Interfacerest REST, API key from the dashboard; Python and JavaScript SDKs
Toolingnot stated
Composes withThe broker's keyed search leg; the 1,000 a month is small against a crawl, and extract bills the same pool
Reliabilityno reliability event recorded
NotesOne credit is not one page: the page states credits are consumed by request type, search, extract or crawl.
Evidence rungdocumented
Checked2026-10-22 (live); stale on 2026-11-21
Parsed numbers
  • $.limits[0].value limit:request-rate 1000.0 credits / month
Evidence (1)
datesourcewhat it proved
2026-10-22www.tavily.com/pricing1,000 free API credits per month with no credit card; credits reset on the first of each month; pay as you go USD 0.008 per credit; Project USD 30 a month
Unknown or withheld values (2)
  • $.reliability_note none-observed
  • $.tooling not-stated

Tavily keyless route Crawling

caveatanonymousno cardRrequest-rate

www.tavily.com/ · search API · crawler-scraper/tavily-keyless · JSON · compare

Free tiera shared public route with no key
unit requests; metered on request-count
Pricenone stated
Per-object capnot applicable: the unit is a request
Retentionno allowance is published
Egressnot applicable: JSON answers
Identityanonymous no key
Limits
  • request-rate 429 with Retry-After 600 s was measured at 02:04Z and a 200 at 02:26Z in the platform recon
Bindingrequest-rate
Interfacerest the same search endpoint without a key
Toolingnot stated
Composes withThe last search leg, kept for the case where every keyed provider is spent
Reliabilityno reliability event recorded
NotesThe clearest measured hold in the topic: 600 seconds. A caller that retries on a shorter clock burns its own budget and learns nothing.
Evidence rungreported not re-run here
Checked2026-10-22 (inherited); stale on 2026-11-05
Evidence (1)
datesourcewhat it proved
2026-10-22withheldprobe outcome rate, 0 failures, this deployment's keyless leg
Unknown or withheld values (3)
  • $.evidence[0].url private-url
  • $.reliability_note none-observed
  • $.tooling not-stated