Integration: guides & tutorials

Chatbase ships two REST API versions. API v1 is the original integration path; API v2 is a modern redesign with structured error codes, cursor-based pagination, Server-Sent Events (SSE) streaming, and a cleaner response contract. This guide covers v2 exclusively — it is the forward path for all new integrations in 2026. By the end, you will know how to authenticate, send streaming chat messages, paginate through conversation history, handle rate limits, and feed fresh website content scraped with Apify into your Chatbase knowledge base.

Prerequisites: API v2 requires a Standard plan or above. Free and Hobby accounts cannot use the API. Check the pricing guide to evaluate upgrading.

Model Context Protocol (MCP) is an open standard for how an AI host (IDE, desktop assistant, or similar) discovers and calls tools in a separate MCP server over transports such as stdio (local) or HTTP (remote). It is a JSON-RPC bridge that standardizes the boundary where models meet APIs, files, and automation. It does not replace your databases or scrapers. The payoff is one reusable integration surface across MCP-capable hosts, provided you still own auth, timeouts, and least privilege.

Below we split what the spec actually defines from what each vendor ships, sketch how the ecosystem shows up in scraping and data workflows, and outline adoption so a chat session does not become root access. For headline news context, see Top 10 AI and tech stories this week (March 17–24, 2026).

Bright Data offers residential, datacenter, ISP, and mobile proxy products behind a single Super Proxy hostname. Correct zone choice and credential format prevent surprise bills (residential is priced per GB) and avoid blocked or unsupported destinations.

This post is a practical setup path: pick a network, provision a zone, verify connectivity, then wire Python, Node.js, or cURL. For teams that do not want to own retry logic and browser farms, Apify is a common managed alternative—Bright Data and Apify are often used together when you need custom proxy pools inside your own code.

n8n is a workflow automation tool that pairs well with Apify because it handles long-running jobs, large JSON payloads, and branching logic without the tight synchronous limits of simpler connectors. This guide covers setup, the official Apify node, webhook patterns for slow Actors, example workflows, and operational tips.