Docs API Reference SDK Reference Agentic Usage AI Skills

Use official Tavily clients with BazaarLink

Point verified Tavily clients and integrations at BazaarLink by changing the base URL and using a BazaarLink API key. This page lists only client behaviour verified from source.

Base URL and authentication

Use https://api.bazaarlink.ai/v1 as the preferred base URL. The previous https://bazaarlink.ai/api/v1 base remains supported. The Python SDK sends Authorization: Bearer and also sends extra X-* headers; BazaarLink accepts those headers.

1
2
Preferred base URL: https://api.bazaarlink.ai/v1
Legacy supported base URL: https://bazaarlink.ai/api/v1

Python: tavily-python

The Python client accepts api_base_url and sends the BazaarLink key as Authorization: Bearer.

1
2
3
4
5
6
7
8
from tavily import TavilyClient

client = TavilyClient(
    api_key="YOUR_BAZAARLINK_API_KEY",
    api_base_url="https://api.bazaarlink.ai/v1",
)

response = client.search("What is new in AI?")

JavaScript: tavily

The official JavaScript tavily factory accepts apiBaseURL. Keep the API key in an environment variable or local secret store.

1
2
3
4
5
6
7
8
import { tavily } from "@tavily/core";

const client = tavily({
  apiKey: process.env.BAZAARLINK_API_KEY,
  apiBaseURL: "https://api.bazaarlink.ai/v1",
});

const response = await client.search("What is new in AI?");

LangChain: langchain-tavily

The verified LangChain classes accept api_base_url. Set it on TavilySearch, TavilyExtract, and TavilyCrawl.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
from langchain_tavily import TavilySearch, TavilyExtract, TavilyCrawl

search = TavilySearch(
    tavily_api_key="YOUR_BAZAARLINK_API_KEY",
    api_base_url="https://api.bazaarlink.ai/v1",
)
extract = TavilyExtract(
    tavily_api_key="YOUR_BAZAARLINK_API_KEY",
    api_base_url="https://api.bazaarlink.ai/v1",
)
crawl = TavilyCrawl(
    tavily_api_key="YOUR_BAZAARLINK_API_KEY",
    api_base_url="https://api.bazaarlink.ai/v1",
)

Plain HTTP

Any HTTP client can call the same endpoint with Authorization: Bearer and a JSON body. The example uses Tavily Search.

1
2
3
4
curl -X POST https://api.bazaarlink.ai/v1/search \
  -H "Authorization: Bearer $BAZAARLINK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"What is new in AI?"}'

Dify and n8n

Use a generic HTTP Request node: POST https://api.bazaarlink.ai/v1/search with Authorization: Bearer and Content-Type: application/json. The official Dify and n8n Tavily nodes have not been verified to allow a custom base URL, so this page does not claim that they do.

1
2
3
4
5
POST https://api.bazaarlink.ai/v1/search
Authorization: Bearer YOUR_BAZAARLINK_API_KEY
Content-Type: application/json

{"query":"What is new in AI?"}

MCP: verified boundary

The official npm tavily-mcp package hard-codes api.tavily.com and cannot be pointed at BazaarLink.

Available now: the remote HTTP MCP endpoint is live at https://api.bazaarlink.ai/v1/mcp. Authenticate with your BazaarLink API key; it exposes search, extract, crawl and map. The unmodified npm tavily-mcp package still hard-codes api.tavily.com and cannot be redirected.

Cursor and Claude Desktop

A separate npm stdio wrapper is optional. Cursor and Claude Desktop both support remote HTTP MCP servers configured with a URL and a header. The following JSON snippets are planned configuration, not a live endpoint claim.

Planned Cursor configuration

1
2
3
4
5
6
7
8
9
10
{
  "mcpServers": {
    "bazaarlink-search": {
      "url": "https://api.bazaarlink.ai/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${env:BAZAARLINK_API_KEY}"
      }
    }
  }
}

Planned Claude Desktop configuration

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
{
  "mcpServers": {
    "bazaarlink-search": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.bazaarlink.ai/v1/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}",
        "--transport",
        "http-only"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_BAZAARLINK_KEY"
      }
    }
  }
}