Brave Search API: what the official pages do not settle

Search (prepaid usage)

Brave Search API (Search plan) · 9 of 19 conditions not settled

• Concurrent requests: not stated. A sentence on Brave Search API's official pages that says how many requests the plan can run at once for this plan would change this verdict.
• Failed requests are not billed: not stated. A sentence on Brave Search API's official pages that says whether requests that fail on the provider side are billed for this plan would change this verdict.
• Billed per successful request: not stated. A sentence on Brave Search API's official pages that says whether only successful requests are billed for this plan would change this verdict.
• Target error responses (e.g. 404) are not billed: not stated. A sentence on Brave Search API's official pages that says whether error responses from the target site are billed for this plan would change this verdict.
• Data storage / processing region: not stated. A sentence on Brave Search API's official pages that says where customer data is stored or processed for this plan would change this verdict.
• Vendor-hosted remote MCP endpoint: not stated. A sentence on Brave Search API's official pages that says whether the provider hosts a remote MCP endpoint for this plan would change this verdict.
• Remote MCP accepts the authentication: not stated. A sentence on Brave Search API's official pages that says how the MCP endpoint signs in (API key or OAuth) for this plan would change this verdict.
• Data processing agreement: not stated. A sentence on Brave Search API's official pages that says whether the vendor offers a data processing agreement for this plan would change this verdict.
• Service level agreement (SLA): not stated. A sentence on Brave Search API's official pages that says whether the plan comes with a service level agreement for this plan would change this verdict.

Verdict for this plan at 100,000 searches a month, as text.