All skills
brave avatar

/spellcheck

@2827ed3 official

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.

Use this Skill: https://skilld.dev/gh/brave/brave-search-skills/spellcheck

This session only. Nothing lands on disk.

SKILL.md

≈48 tokens always: the name and description. ≈526 when used: this file.

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

Source: SKILL.md on GitHub

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill is a legitimate documentation file for the Brave Search Spellcheck API. It demonstrates how to call the service using environment variables for authentication and contains no malicious code, obfuscation, or unauthorized data access patterns.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    1/1 file flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 2827ed3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 8 months ago
  • spellcheck
  • brave-search
  • search-api
  • query-correction
  • nlp
  • text-processing

README badge

README badge for brave/brave-search-skills/spellcheck

Corrects misspelled search queries via the Brave Search API, returning a normalized version for pre-search cleanup or "Did you mean?" UI. Most Brave search endpoints include spellcheck by default; use this skill as a standalone step when you need corrections before deciding which endpoint to call.

Generated from the current SKILL.md.

Do I need a separate API key for this skill?
Yes. You need a Brave Search API key from https://api.search.brave.com and must be subscribed to the Spellcheck plan.
When should I use this instead of the spellcheck built into Web Search?
Use this standalone endpoint when you need spell correction before deciding which search endpoint to call, or to show a "Did you mean?" suggestion to users before running a search. Web Search and LLM Context have spellcheck built in by default.
What languages does this support?
51 language codes are supported, including en, fr, de, pt-br, and zh-hans. Pass the language code via the lang parameter.
What happens if a query has no spelling errors?
The results array will be empty, and only the original query is returned.

Generated from the current SKILL.md. These answers refresh after source changes.