spellcheck

Original：🇺🇸 English
Translated

USE 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.

5installs
Sourcebrave/brave-search-skills
Added on

NPX Install

npx skill4agent add brave/brave-search-skills spellcheck

Tags

Translated version includes tags in frontmatter
spellcheck-apitext-processingapi-integrationsearch-toolquery-normalization

SKILL.md Content

View Translation Comparison →

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)

bash
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

http
GET https://api.search.brave.com/res/v1/spellcheck/search
Authentication: 
X-Subscription-Token: <API_KEY>
header

Parameters

ParameterTypeRequiredDefaultDescription
q
stringYes—Query to spell check (1-400 chars, max 50 words)
lang
stringNo
en
Language preference (2+ char language code, e.g. 
en
, 
fr
, 
de
, 
pt-br
, 
zh-hans
). 51 codes supported
country
stringNo
US
Search country (2-letter country code or 
ALL
)

Response Fields

FieldTypeDescription
type
stringAlways 
"spellcheck"
query.original
stringThe input query as submitted
results
arraySpell-corrected suggestions. May be empty when no correction is found
results[].query
stringA corrected version of the query

Example Response

json
{
  "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