AAES
Book a demo

Capability library / Application package

Brave Search package v1.0.0

Brave Search API web search: run one read-only web search and return titles, URLs and descriptions for research with citations.

Review state: In review · Not part of the reviewed release library

This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern

Before you enable this package

Draft package; not part of the reviewed library. Keep api.search.brave.com. The package registers one web search sent as a POST, so the query travels in the request body, and a request contract limits the body to the query and a few search options. Search queries leave your deployment and go to Brave. Brave's API terms forbid storing or caching results beyond what your application needs at the time, and forbid using them to train or evaluate models.

Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.

Capabilities (1)

Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/brave.json and embeds a copy in the release binary.

Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. A minimum tier does not measure the operation's business or confidentiality risk.

Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.

brave.web.search v1.0.0R0

Kind
tool
Action
read
Endpoint
POST https://api.search.brave.com/res/v1/web/search
Connector
http
Custody
inherits the pack credential block
Credential ref
inherits the pack credential block
Data class
internal

Search web.

Run one web search and return Brave's results: web.results[] with title, url and description for each page. The method is POST, with the query in the body, but the effect is a read, so it sits at the R0 floor. The query text is sent to Brave, so the capability is classed internal.

Credential reference

The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.

Reference
secret-ref-brave-search-api-key
Custody
customer_vault
Injection
header (X-Subscription-Token)

Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.

Complete credential requirements

A Brave Search API subscription token, held only in the client's own secret manager under this reference and resolved at execution. The stored material is the bare token, the complete X-Subscription-Token header value; Brave's reference calls it the subscription token generated for the product. The token is created and revoked in the Brave Search API dashboard; the retrieved pages document no expiry, so rotation and revocation are administrative actions the deployment owns, and a revoked value fails closed at Brave. The caller never supplies the token, and the connector refuses a caller-supplied credential header. Executor hygiene: the value must live only in executor memory for the lifetime of a call, must never be written to logs, traces or diagnostics, and must not appear in crash dumps.

Resources

  • brave-web-search (api, internal): https://api.search.brave.com/res/v1/web/search

Technical package and review record

Complete provider requirements and exclusions

This pack registers one capability, brave.web.search, for the research-with-citations skill. It calls the documented POST form of the Web Search endpoint, https://api.search.brave.com/res/v1/web/search, with the query in the request body. The GET form takes the query in the URL, and the connector dials the registered URL and ignores a caller's query string, so GET could not carry a query. Egress is the one host api.search.brave.com.

A request contract admits only these body fields: q (required; Brave allows at most 600 characters and 75 words), count (Brave allows 1 to 20, default 20), offset (0 to 9), country, search_lang, safesearch (off, moderate or strict; Brave's default is moderate), freshness and extra_snippets. Every other field is refused before dispatch, including goggles, summary and the rich-callback options. The connector does not check the numeric ranges or the query length; Brave rejects values outside them.

The capability is a read at the R0 floor. The search results are public web content, but the query text leaves the deployment and goes to Brave, and an agent's query can carry internal context, so the capability is classed internal. Policy decides who may search and how often; Brave counts only successful requests against the plan quota and reports X-RateLimit-Limit, X-RateLimit-Policy, X-RateLimit-Remaining and X-RateLimit-Reset headers.

Terms to review before enabling, from Brave's Search API terms of use (last updated 1 September 2026): a customer may not store, cache or build a database of search results beyond the transient storage the application needs, may not redistribute or resell them, and may not use them to create, evaluate, train, fine-tune or benchmark models. An order form can change these terms. Attribution is optional. A research workflow that cites a result should cite the source page's URL and keep only what the answer needs.

Not registered: the other Brave endpoints (news, image, video, suggest, spellcheck, local points of interest, summarizer and AI answers), the GET form of web search, and Goggles. AAES has not been certified by Brave; the endpoint is configuration to review and test, and the vendor has not endorsed it.

Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.

The full documentation review record is supplied in the evaluation package. The evaluation package runs in your environment and comes only with the paid design partnership. This page reproduces the source links and review block; the full record is available for evaluation. Discuss a design partnership to inspect it before installation.

Review block

This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.

Review in progress; record dated 2026-10-29

5 sources, retrieved 2026-10-29

Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed or yet tested against a live provider tenant.

Release identity

SHA-256 of the pack file bytes: ad8c52b796783bc85c0e91ae9188b80c88ab684b9a84d74950f6cdc7facca4ae

Not part of the reviewed release library. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.

← Back to the capability library