Tools

Tavily

AI search, extract, crawl, and map
View as Markdown

Proxies Tavily’s AI-search API. The gateway exposes Tavily’s sibling endpoints under /tavily, all on the single host api.tavily.com:

POST /tavily/<endpoint>   → https://api.tavily.com/<endpoint>

POST only — the method Tavily’s action endpoints document. Every control travels in the JSON body and is forwarded unchanged.

Endpoints

The gateway accepts exactly this whitelist; any other subpath returns the gateway’s 404 without reaching Tavily.

EndpointPurpose
searchAI web search
extractExtract content from URLs
crawlCrawl a site
mapMap a site’s URLs

Tavily’s /usage endpoint (account-wide credit/limit metadata) is deliberately not exposed — per-client tokens have no business reading the shared account’s usage.

What the gateway injects and strips

Tavily authenticates with the Authorization: Bearer header — the same header you use for your gateway token. So the gateway overwrites it with the injected Tavily key:

  • The Authorization header is overwritten with the secret Tavily key. Your gateway token is consumed by the gateway and never reaches Tavily.
  • Tavily has no query-param spelling of the key, so nothing is dropped from the query string.

Examples

$curl -X POST "$GATEWAY/tavily/search" \
>  -H "Authorization: Bearer $TOKEN" \
>  -H "Content-Type: application/json" \
>  -d '{"query": "latest cloudflare workers features"}'

The response is Tavily’s JSON, returned unchanged. For request and response fields, follow Tavily’s documentation — the gateway does not alter them.