Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brave Search API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrave.com%2Fbrave" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrave.com%2Fbrave" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Brave Search API.
Query the web index for search results
Retrieve news, image, and video results for a query
Look up local points of interest and their descriptions
Serve autocomplete suggestions for a partial query
Return spell-check corrections for a typed query
GET STARTED
Patterns agents use Brave Search API for, with concrete tasks.
★ AI agent web search grounding
A research agent needs fresh, independent web results to ground its answers instead of relying on stale training data. Through Jentic the agent sends the user's query to Brave's web search, reads the ranked results, and can follow up with news or video results for the same topic. Because the results come from Brave's own index, the agent gets a source it can cite rather than a black-box summary.
Search Jentic for 'search the web', call GET /web/search with the user's query, then optionally GET /news/search for recent coverage of the same topic.
News monitoring
A monitoring workflow needs recent coverage of a topic on a schedule. The news search operation returns current articles for a query, so an agent can poll for a brand or keyword and surface new results. This lets a briefing assistant assemble a digest without a person searching by hand.
Call GET /news/search with the tracked keyword on a schedule and diff the results against the last run to surface new coverage.
Local place lookup
A location-aware assistant needs details about nearby places for a query. The points-of-interest and descriptions operations return local results and their summaries, so an agent can answer 'coffee near the office' with real places rather than a generic web page. This grounds local questions in structured place data.
Call GET /local/pois for the query and location, then GET /local/descriptions to fetch a summary for the returned places.
Query autocomplete and correction
A search-box experience needs to suggest completions and fix typos as a user types. The suggest and spellcheck operations return autocomplete candidates and corrected spellings for a partial or misspelled query, so an agent can offer suggestions before running the full search.
Call GET /suggest/search for completions as the user types, and GET /spellcheck/search to correct a misspelled query before searching.
8 endpoints — the brave search api returns independent search results across the web, news, images, and video.
METHOD
PATH
DESCRIPTION
/web/search
Search the web index
/news/search
Retrieve news results
/images/search
Retrieve image results
/videos/search
Retrieve video results
/local/pois
Look up local points of interest
/local/descriptions
Fetch descriptions for local places
/suggest/search
Get autocomplete suggestions
/spellcheck/search
Get spell-check corrections
/web/search
Search the web index
/news/search
Retrieve news results
/images/search
Retrieve image results
/videos/search
Retrieve video results
/local/pois
Look up local points of interest
/local/descriptions
Fetch descriptions for local places
/suggest/search
Get autocomplete suggestions
/spellcheck/search
Get spell-check corrections
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Brave Search API by hand means provisioning a subscription token, attaching it to the right header, and building each search call yourself. Through Jentic you install once, store the token, and import it from the API Directory, and your agent calls it without you writing the client.
Permission scoping
The Brave Search API exposes web, news, image, video, local, and suggestion operations, so a rule bounds which of them the agent may call: web and news search without the local or suggestion operations unless you add them. You choose the allowed set, so the agent only runs the operations you pick.
Credential isolation
You store the subscription token once and Jentic keeps it server-side, so it never sits in the agent's prompt or context; the agent calls the search operations and the token is attached to the request header out of band.
Intent-based discovery
Agents search Jentic by intent such as 'search the web' or 'find local points of interest', and Jentic returns the matching Brave Search operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Brave Search API through Jentic.
Is there a Brave Search API MCP server?
You don't need an MCP server to give your agent the Brave Search API. Jentic connects it directly from the API Directory: import it, store your subscription token once, and your agent calls the web, news, image, and local operations on demand without loading another server's tool definitions into its context.
What authentication does the Brave Search API use?
The Brave Search API authenticates with a subscription token sent in a request header on each call. When you connect it through Jentic, the token is stored server-side, so it stays out of the agent's prompt while the agent still makes the search calls.
Can I search the web with the Brave Search API?
Yes. GET /web/search returns ranked results from Brave's own index for a query, and GET /news/search, GET /images/search, and GET /videos/search return news, image, and video results for the same query, so an agent can ground an answer in fresh, citable sources.
What are the rate limits for the Brave Search API?
The OpenAPI spec does not state rate limits for the Brave Search API; Brave sets them by subscription plan. Cache repeat queries where you can and check your plan in the Brave Search API dashboard, since the spec does not carry the limit.
How do I run a local place lookup through Jentic?
Search Jentic for 'find local points of interest', load the matching operation, and call GET /local/pois with the query and location. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Brave Search API?
Yes. Because Jentic One is self-hosted, you decide which operations the agent may call: you might allow web and news search with GET /web/search and GET /news/search while withholding the local operations, and every call the agent makes is logged.
For Agents
Query Brave's independent search index for web, news, image, and video results, look up local points of interest, and fetch autocomplete suggestions and spell-check corrections.
Use for: Search the web for a query and return results, Retrieve recent news results for a topic, Find image results for a search term, Get video results for a query
Not supported: Does not handle result hosting, ad placement, or account billing. Use for Brave web, news, image, video, local, and suggestion search only.
The Brave Search API returns independent search results across the web, news, images, and video. It queries the web index, retrieves news, image, and video results, and returns points of interest and their descriptions for local search. It also serves autocomplete suggestions for a partial query and spell-check corrections for a typed one. Each result set is drawn from Brave's own index rather than a syndicated one. Requests authenticate with a subscription token sent in a request header.