Tavily keyless
tavily.com · 2 records in Crawling · JSON
Records 2
- caveatTavily
Crawlingfree tieridentity emailno cardlimit request-rateevidence documentedstale on 2026-11-22
- caveatTavily keyless route
Crawlingfree tieridentity anonymousno cardlimit request-rateevidence reportedstale on 2026-11-14
Tavily
Crawling- Free allowance
- 1,000 API credits a month, no credit card, reset on the first of the month
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- request-rate1,000 credits a month; requests stop when they are spent until the reset or an upgrade; USD 0.008 per credit pay-as-you-go; Project plan USD 30 a month
- Evidence
- documented1 source; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | 1,000 API credits a month, no credit card, reset on the first of the month unit requests; metered on request-count |
|---|---|
| Price | none stated |
| Limits | |
| Identity | email no credit card stated |
| Egress | not applicable |
| Retention | credits reset monthly and do not carry over |
| Interface | rest REST, API key from the dashboard; Python and JavaScript SDKs |
| Tooling | not stated |
| Composes with | The 1,000 a month is small against a crawl, and extract bills the same pool |
| Reliability | no reliability event recorded |
| Notes | One credit is not one page: the page states credits are consumed by request type, search, extract or crawl. |
| Parsed numbers |
|
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | www.tavily.com/pricing | 1,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 values 4
- egress terms: the field does not apply to this kind of offer
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- tooling: a source was read and is silent on this field
Tavily keyless route
Crawling- Free allowance
- Search and Extract free with no account and no API key, rate-limited; the keyless cap is not published
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- request-rate429 with Retry-After 600 s was measured at 02:04Z and a 200 at 02:26Z in the platform recon
- Evidence
- reported6 sources; a third party said so
- Freshness
- stale on 2026-11-14checked 2026-10-30 (live); stale on 2026-11-14
| Free tier | Search and Extract free with no account and no API key, rate-limited; the keyless cap is not published unit requests; metered on request-count |
|---|---|
| Price | none stated |
| Limits |
|
| Identity | anonymous no account and no API key; each request carries the header X-Tavily-Access-Mode: keyless |
| Egress | not applicable |
| Retention | no allowance is published |
| Interface | rest POST https://api.tavily.com/search or /extract with the header X-Tavily-Access-Mode: keyless, or the remote MCP at mcp.tavily.com/mcp/ with the same header; Crawl, Map and Research need a key |
| Tooling | not stated |
| Composes with | The last search leg, kept for the case where every keyed provider is spent |
| Reliability | no reliability event recorded |
| Notes | The clearest measured hold in the topic: 600 seconds. A caller that retries on a shorter clock burns its own budget and learns nothing. |
| Evidence note | reported free tier, identity and route quoted from the vendor's keyless page; the hold length in limits is reported and not re-measured, because the route takes POST and a GET probe cannot exercise it |
| Parsed numbers |
|
Evidence 6
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | source not published | probe outcome rate, 0 failures, this deployment's keyless leg |
| 2026-10-30 | docs.tavily.com/documentation/keyless | Search and Extract are free with no account and no API key |
| 2026-10-30 | docs.tavily.com/documentation/keyless | the keyless route is the ordinary POST to /search or /extract with the X-Tavily-Access-Mode: keyless header, and the remote MCP takes the same header; Crawl, Map and Research need a key |
| 2026-10-30 | docs.tavily.com/documentation/keyless | the keyless route is rate-limited and the page publishes no number for the cap |
| 2026-10-30 | docs.tavily.com/documentation/rate-limits | keyless limits are separate from the keyed 100 and 1,000 requests a minute, and no keyless number is published |
| 2026-10-30 | probe: https://api.tavily.com/search?query=wikipedia | a GET to the keyless search route answers 405 Method Not Allowed: the route takes POST, which a GET probe cannot exercise |
Unknown values 4
- egress terms: the field does not apply to this kind of offer
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- tooling: a source was read and is silent on this field