Spellcheck
Requires API Key: Get one at https://api.search.brave.com Plan: Included in the Spellcheck plan. See https://api-dashboard.search.brave.com/app/subscriptions/subscribe
Quick Start (cURL)
curl -s "https://api.search.brave.com/res/v1/spellcheck/search" \
-H "Accept: application/json" \
-H "X-Subscription-Token: ${BRAVE_SEARCH_API_KEY}" \
-G \
--data-urlencode "q=artifical inteligence" \
--data-urlencode "lang=en" \
--data-urlencode "country=US"
Endpoint
GET https://api.search.brave.com/res/v1/spellcheck/search
Authentication: X-Subscription-Token: <API_KEY> header
Parameters
| Parameter | Type | Required | Default | Description |
|---|
q | string | Yes | — | Query to spell check (1-400 chars, max 50 words) |
lang | string | No | en | Language preference (2+ char language code, e.g. en, fr, de, pt-br, zh-hans). 51 codes supported |
country | string | No | US | Search country (2-letter country code or ALL) |
Response Fields
| Field | Type | Description |
|---|
type | string | Always "spellcheck" |
query.original | string | The input query as submitted |
results | array | Spell-corrected suggestions. May be empty when no correction is found |
results[].query | string | A corrected version of the query |
Example Response
{
"type": "spellcheck",
"query": {
"original": "artifical inteligence"
},
"results": [
{
"query": "artificial intelligence"
}
]
}
Use Cases
- Pre-search query cleanup: Check spelling before deciding which search endpoint to call
- "Did you mean?" UI: Show users a corrected suggestion before running the search
- Batch query normalization: Clean up user inputs in bulk
Notes
- 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 - Context-aware: Corrections consider the full query context, not just individual words
