100 free credits — no credit card required.Start building
Logo
Tavily logoTavily API

Search the web with Tavily on one API

Run Tavily web search, extract, map, and crawl as structured JSON with one SocialCrawl API key. Same success envelope and credit model as every other platform. Reads are priced in credits.

Tavily logo
/v1/tavily

4 active endpoints. Standard tier, 1 credit each.

  • GET /v1/tavily/search
  • GET /v1/tavily/extract
  • GET /v1/tavily/map
  • GET /v1/tavily/crawl

What Tavily endpoints does SocialCrawl ship?

Four live read endpoints for Tavily web grounding. Search with optional answer, multi-URL extract, site map, and multi-page crawl. Data API only. No second Tavily account required on your side.

Web search

1 credit
/v1/tavily/search

Ranked web results for a natural-language query. Optional include_answer for an LLM synthesis. Depth, topic, time_range, domain filters, and max_results control scope.

query, search_depth, topic, time_range, max_results, include_answer, include_domains, exclude_domains

URL extract

1 credit
/v1/tavily/extract

Clean text from one URL or a CSV of up to 20. Markdown or text format. Advanced extract depth for harder pages. Failed URLs are reported alongside successes.

urls (CSV, max 20), extract_depth, format

Site map

1 credit
/v1/tavily/map

Discover URLs from a root without full page bodies. Depth, breadth, limit, and path or domain filters. Faster than crawl when you only need coverage.

url, depth, breadth, limit

Site crawl

1 credit
/v1/tavily/crawl

Multi-page crawl with extracted content per page. Natural-language instructions guide path selection. Same filter family as map, plus extract depth and format.

url, limit, extract_depth, format

Tavily API4 endpoints supported
View docs

Returns ranked web search results for a query, and optionally a written answer put together from the top sources.

Use it when you want search results you can narrow by domain, date, or topic, with a short written answer alongside them if you ask for one.

GET/v1/tavily/search?query=claude+opus+4.7+release+notes

query · The search query — natural-language free text.

$ curl https://www.socialcrawl.dev/v1/tavily/search?query=claude+opus+4.7+release+notes \
    -H "x-api-key: sc_YOUR_API_KEY"
— · idle
// Running this live needs your own API key — hit "Try it" to see an example response

How the Tavily API works

Tavily is a normal SocialCrawl surface. You call GET /v1/tavily/… with an API key, spend credits on live misses, and get a single JSON envelope back. Web grounding without holding a second Tavily key in your app.

Authenticate every call

Send your key in the x-api-key header. The same key works for social platforms, Universal Search, Google Trends, and Tavily.

GET with query params

All four routes are GET. Pass query, urls, or url plus optional depth and filter params. We map query strings into Tavily's JSON body server-side before upstream.

Pay in credits, not seats

Each live miss costs 1 credit (standard tier). Cache hits cost 0. Empty or hard failures refund. Bad params return 400 with no charge.

Read one JSON envelope

Every response is success, data, credits_used, credits_remaining, request_id, cached. Search may include results and answer. Extract, map, and crawl return their Analytics payloads under data.

The usual integration chain

Most products search first, extract the winners, map a docs root when coverage matters, then crawl only the paths they need.

01Search
GET /v1/tavily/search?query=…

Ranked results[] and optional answer

Find candidate URLs and a short synthesis before deeper reads.

02Extract
GET /v1/tavily/extract?urls=…

Clean content rows per URL (up to 20)

Turn result links into AI-ready text without a second scraper.

03Map
GET /v1/tavily/map?url=…

Discovered URL list from a root

Enumerate site structure before paying for full page bodies.

04Crawl
GET /v1/tavily/crawl?url=…

Pages with extracted content under instructions

Pull multi-page docs or product trees in one guided run.

request
GET /v1/tavily/search
  ?query=best+web+scraping+apis
  &include_answer=true
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

GET /v1/tavily/extract?urls=https://example.com
response envelope
{
  "success": true,
  "data": {
    "results": [],
    "answer": "…"
  },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Tavily routes use the Analytics archetype so answer, results, and crawl rows are not stripped by list-only mappers.

Analytics (search)search

results[] ranked hits; optional answer; query metadata (depth, time_taken, total_results)

Analytics (extract)extract

per-URL content rows, format, failures listed alongside successes

Analytics (map / crawl)map, crawl

map: URL list from sitegraph; crawl: pages with extracted content

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. Tavily is not a sidecar SDK in your process.

  1. 01

    Edge receives the call

    Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

  2. 02

    Validate, then debit

    Registry lookup finds tavily/search, extract, map, or crawl. Required params (query, urls, or url) are checked first. Invalid input returns 400 with no charge. Valid calls debit 1 credit atomically before upstream work.

  3. 03

    Cache or fetch

    A deterministic cache key is built from platform, resource, and params. Hit: return immediately, credits_used = 0. Miss: SocialCrawl's Tavily fetcher POSTs to api.tavily.com with house credentials. You do not attach a Tavily bearer token.

  4. 04

    Normalize and return

    Upstream JSON is kept under the Analytics archetype (including answer on search), wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

  • Live miss on search: 1 credit
  • Live miss on extract: 1 credit
  • Live miss on map: 1 credit
  • Live miss on crawl: 1 credit
  • Cache hit: 0 credits
  • Empty / hard fail: auto-refund
  • Bad params: 400, never charged
  • No credits: 402, never charged
  • No second Tavily account required for app auth

How we get the data

Tavily is web grounding for agents and research. We proxy the four public operations so your product stays on one SocialCrawl key.

What Tavily is for this API

Web search with optional answer, clean URL extract, sitegraph map, and multi-page crawl. Complements social reads when you need open-web context.

How SocialCrawl reaches it

Dedicated Tavily fetcher translates GET query params into Tavily's JSON POST body. Upstream is api.tavily.com with SocialCrawl house auth. Your app only sends x-api-key.

What leaves our edge

A unified JSON envelope: success, data, credits_used, request_id, cached. Search preserves results and answer. Extract, map, and crawl return their native Analytics payloads.

What we do not ship live

No Tavily dashboard login. No write or index management. extract is capped at 20 URLs per call. map returns URLs without full bodies unless you crawl.

field map sketch
ranked web hits + answerAnalytics results/answerranked web hits plus optional synthesized answer
page body per URLextract content rowscleaned page body per requested URL
sitegraph / crawl pagesURL list + contentsitegraph URL list or crawl pages with content

What this API is used for

The jobs this API is most often used for.

4active Tavily endpoints in the registry
1 crcredits per live Tavily call

Agent web grounding and docs ingestion

Callers use search with include_answer for grounding, extract for result URLs, and map then crawl for documentation trees. Same key as social endpoints reduces tool sprawl. Full Tavily surface on the SocialCrawl key at 1 credit per live call. No second vendor account in the customer app for these four routes.

Search and extract are typically a few seconds on live miss. Map and crawl scale with depth, breadth, and limit. Cache hits return immediately at 0 credits.

What people build with the Tavily API

The jobs Tavily data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

RAG and agent builders

Python, LangChain-style tools, workers

search with include_answer for grounding, then extract on cited URLs before embedding.

Docs and research jobs

Node, cron, storage pipelines

map a docs root, then crawl with instructions to pull only API or product pages.

Full-stack product teams

TypeScript, Explorer, same SocialCrawl key

Add open-web context next to social reads without provisioning a separate Tavily key in production.

Call it in two lines

Each live Tavily call is 1 credit. Cache hits are free. Search takes query. Extract takes urls. Map and crawl take a root url.

curl "https://www.socialcrawl.dev/v1/tavily/search?query=best+web+scraping+apis&include_answer=true" \
  -H "x-api-key: sc_your_api_key_here"
curl "https://www.socialcrawl.dev/v1/tavily/extract?urls=https://example.com" \
  -H "x-api-key: sc_your_api_key_here"
Tavily logoTavily on SocialCrawl

Same key as the rest of the catalog

Endpoints

What data does the Tavily API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

Comparison

How does SocialCrawl compare to Tavily API (direct) for Tavily data?

Same Tavily data, two very different paths. Auth, rate limits, schema, and cost — side by side.

Authentication

SocialCrawl
One x-api-key shared with 47 other platforms
Tavily API (direct)
Separate Tavily account and API key

Setup

SocialCrawl
GET requests at /v1/tavily/{resource} in the same envelope as your other sources
Tavily API (direct)
Tavily SDK or REST with its own response format

Pricing

SocialCrawl
1 credit per call from one shared balance
Tavily API (direct)
Separate plan with its own monthly credit allotment

Response schema

SocialCrawl
Unified SocialCrawl JSON envelope across search, extract, map, and crawl
Tavily API (direct)
Tavily-native response shapes

Data coverage

SocialCrawl
Search, extract, map, and crawl, plus Perplexity and social search on the same key
Tavily API (direct)
Full Tavily surface with every native parameter

Free tier

SocialCrawl
100 free credits, no credit card
Tavily API (direct)
Free tier with monthly credits on Tavily's own plan
FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
What is the Tavily API on SocialCrawl?
SocialCrawl gives you access to the Tavily web-search API through your single SocialCrawl x-api-key and credit balance. Tavily is a search API built for AI agents and LLMs. You call it at /v1/tavily/{resource} on the same key as your social, dev, and search data, no separate Tavily account.
Which Tavily endpoints does SocialCrawl offer?
4 endpoints: Search, Extract, Map, and Crawl. Each is a GET at /v1/tavily/{resource}.
Do I need a separate Tavily API key?
No. Your SocialCrawl x-api-key covers Tavily. You do not register at api.tavily.com or manage a second key. SocialCrawl proxies the request and bills it from your existing credit balance, the same way every other SocialCrawl endpoint works.
How much does the Tavily API cost on SocialCrawl?
Tavily endpoints run on the standard tier at 1 credit per call. New accounts get 100 free credits with no credit card required, enough to test search, extract, map, and crawl many times over before you pay anything.
Can I also reach Perplexity or AI search from the same key?
Yes. The same SocialCrawl key reaches Perplexity Sonar for research and SocialCrawl's own AI social search across 14 platforms. One key gives you Tavily AND Perplexity AND social search. Pick the backend that fits the query without juggling accounts.
When should I use search vs crawl vs map vs extract?
Use search to find pages for a query, extract to read the content of URLs you already have, map to discover a site's link structure fast, and crawl to walk a site following LLM-chosen paths and pull content. Search and extract suit RAG; map and crawl suit site ingestion.
What is the best way to access Tavily search via API?
Going direct to Tavily gives you the full native surface and its own free tier. SocialCrawl makes sense when Tavily is one of several backends: search, extract, map, and crawl run at 1 credit per call on the same x-api-key as Perplexity Sonar and social search, with 100 free credits to start, no card.
Is there a Tavily data API?
Tavily is itself a web-search API, so the data API is Tavily's own and available directly with its free tier. SocialCrawl adds convenience rather than access: it proxies Tavily search, extract, map, and crawl under one x-api-key so you reach genuine Tavily on the same key and credits as Perplexity Sonar and social search, at 1 credit per call.
Is scraping Tavily data legal?
SocialCrawl returns publicly available Tavily data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction — you are responsible for complying with Tavily's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
Tavily scraping API vs the official Tavily API — what's the difference?
With SocialCrawl there is no app review or approval queue — sign up and call Tavily endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Read the Tavily API reference in the docs

🤖 AI agent or LLM? Read this page as markdown