One built-in platform engine, eight you connect with your own key. The query is a single field in JSON.
Answer synthesis with [N] citations
General-purpose, domain and time filters
Private search, optional synthesizer
Semantic, neural-network based
Citations, follow-up questions
Real-time web crawl
Sonar models, deep research
Research only, iterative loop
Search with publication dates
Full capability matrix — GET /v1/search/providers. Selection cascade: your key portal key platform
Four scenarios our customers roll out first — and see a return right away.
A rep opens a lead card in Bitrix24 — the bot calls /v1/search and brings back fresh company news. Speeds up call prep.
The product team runs /v1/research: "compare the top 5 solutions for X". In 30–60 seconds — a report with links, instead of 1–2 days of analyst work.
A chatbot in Bitrix24 answers questions about exchange rates, order statuses and company news — the data is pulled in real time.
A daily bot searches for brand mentions (time_range=day) and posts a digest to the team chat. No separate subscription to a monitoring service.
Connecting takes minutes — pick the spot where your AI should see the web.

The platform bot calls /v1/search over REST from its message handler. A ready recipe + snippet in the dashboard.

Plug /v1/search in as an agent tool. The agent decides when to search the web and cites the sources in its answer.

Any app via the X-Api-Key header. A Tavily-compatible schema makes migration trivial.
All three ways draw from a shared Vibe balance or use your own BYOK key — the USER PORTAL PLATFORM cascade works automatically.
Paste this prompt into Cursor, Claude Code, Windsurf or ChatGPT — the agent reads /v1/me itself, understands the API schema and wires up search.
My API key for the VibeCode platform: <key> Documentation: https://vibecode.bitrix24.com/v1/me Use Bitrix AI-поиск (POST /v1/search) in this project to perform a web search per the user's request
The prompt works with any modern AI agent — it pulls the response schema itself, sorts out auth and fills in the right parameters.
vibe_api_…); the vibe:search scope is added automatically For developers who prefer to write by hand — there are native SDKs for JavaScript, Python, TypeScript and cURL.
All available in the dashboard right next to this prompt.
BYOK zeroes out platform billing: you pay the provider directly, we only route the request and log the spend. The key is validated on the fly when you add it.

Sign up with Tavily, Brave, Exa or any of the 8 providers and copy the API key. Many offer a free tier to start.

Open /search → "+ Add key". The platform validates the key with the provider right away — if it's invalid, it tells you.

Set provider: "tavily" in the request — or rely on the default key. The USER → PORTAL → PLATFORM cascade kicks in automatically.
Portal admins get PORTAL BYOK — one key for all users. Configured via Web search in the platform dashboard.
The query goes to the provider without your CRM context — you pass only the query. Keys are encrypted in the database with AES-256-GCM. Every call is written to the audit log.
On a provider error your balance is not charged. The response is 502 UPSTREAM_ERROR. You can configure a BYOK fallback through the cascade.
On the platform — 5 Vibes. The 1000-Vibe welcome bonus covers 200 queries. On BYOK — 0 Vibes on the platform, you pay the provider directly.
bitrix-search (the default) synthesizes the answer with [N] citations and an SSE streaming mode. The other 8 are tuned for the broad English-language web.