$npx -y skills add brave/brave-search-skills --skill spellcheckUSE FOR spell correction. Returns corrected query if misspelled. Most search endpoints have spellcheck built-in; use this only for pre-search query cleanup or "Did you mean?" UI.
| 1 | # Spellcheck |
| 2 | |
| 3 | > **Requires API Key**: Get one at https://api.search.brave.com |
| 4 | > |
| 5 | > **Plan**: Included in the **Spellcheck** plan. See https://api-dashboard.search.brave.com/app/subscriptions/subscribe |
| 6 | |
| 7 | ## Quick Start (cURL) |
| 8 | |
| 9 | ```bash |
| 10 | curl -s "https://api.search.brave.com/res/v1/spellcheck/search" \ |
| 11 | -H "Accept: application/json" \ |
| 12 | -H "X-Subscription-Token: ${BRAVE_SEARCH_API_KEY}" \ |
| 13 | -G \ |
| 14 | --data-urlencode "q=artifical inteligence" \ |
| 15 | --data-urlencode "lang=en" \ |
| 16 | --data-urlencode "country=US" |
| 17 | ``` |
| 18 | |
| 19 | ## Endpoint |
| 20 | |
| 21 | ```http |
| 22 | GET https://api.search.brave.com/res/v1/spellcheck/search |
| 23 | ``` |
| 24 | |
| 25 | **Authentication**: `X-Subscription-Token: <API_KEY>` header |
| 26 | |
| 27 | ## Parameters |
| 28 | |
| 29 | | Parameter | Type | Required | Default | Description | |
| 30 | |--|--|--|--|--| |
| 31 | | `q` | string | **Yes** | — | Query to spell check (1-400 chars, max 50 words) | |
| 32 | | `lang` | string | No | `en` | Language preference (2+ char language code, e.g. `en`, `fr`, `de`, `pt-br`, `zh-hans`). 51 codes supported | |
| 33 | | `country` | string | No | `US` | Search country (2-letter country code or `ALL`) | |
| 34 | |
| 35 | ## Response Fields |
| 36 | |
| 37 | | Field | Type | Description | |
| 38 | |--|--|--| |
| 39 | | `type` | string | Always `"spellcheck"` | |
| 40 | | `query.original` | string | The input query as submitted | |
| 41 | | `results` | array | Spell-corrected suggestions. May be empty when no correction is found | |
| 42 | | `results[].query` | string | A corrected version of the query | |
| 43 | |
| 44 | ## Example Response |
| 45 | |
| 46 | ```json |
| 47 | { |
| 48 | "type": "spellcheck", |
| 49 | "query": { |
| 50 | "original": "artifical inteligence" |
| 51 | }, |
| 52 | "results": [ |
| 53 | { |
| 54 | "query": "artificial intelligence" |
| 55 | } |
| 56 | ] |
| 57 | } |
| 58 | ``` |
| 59 | |
| 60 | ## Use Cases |
| 61 | |
| 62 | - **Pre-search query cleanup**: Check spelling before deciding which search endpoint to call |
| 63 | - **"Did you mean?" UI**: Show users a corrected suggestion before running the search |
| 64 | - **Batch query normalization**: Clean up user inputs in bulk |
| 65 | |
| 66 | ## Notes |
| 67 | |
| 68 | - **Built-in alternative**: Web Search and LLM Context have `spellcheck=true` by default — use this standalone endpoint only when you need the correction before searching |
| 69 | - **Context-aware**: Corrections consider the full query context, not just individual words |