Grammar Checker
Proofread any text and review each suggested fix in place: take it, keep your wording, then copy the result.
- Next.js
- TypeScript
Fix spelling and grammar errors before user submissions get saved.
Grammar Check is a grammar checker and spell check API for English text that inspects text for spelling and grammar errors, returning the corrected wording, error count, and a modified flag. Paid plans add detailed rule descriptions, character offsets, and suggestions for every detected mistake.
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"modified": true,
"corrected": "The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy",
"errorCount": 3,
"dialect": "American",
"corrections": [
{
"rule": "Repetition",
"message": "Did you mean to repeat this word?",
"position": {
"start": 0,
"end": 7
},
"suggestions": [
"The"
]
},
{
"rule": "Spelling",
"message": "Did you mean `because`?",
"position": {
"start": 71,
"end": 78
},
"suggestions": [
"because"
]
},
{
"rule": "Spelling",
"message": "Did you mean `puppy`?",
"position": {
"start": 93,
"end": 101
},
"suggestions": [
"puppy",
"puppetry"
]
}
]
}
}
Proofread any text and review each suggested fix in place: take it, keep your wording, then copy the result.
A grammar check API and spell check API for proofreading user-written text. Pass any raw string in the request body to scan it for grammatical issues and misspelled words, and get back whether anything needed fixing, how many issues were found, and a corrected copy of the text.
It fits anywhere people type prose that others will read: support replies, product reviews, listings, comments, emails and form fields. Run it before saving to flag sloppy submissions, or show the corrected version as a one-click fix. Typical catches include misspellings like "becuase" and "tomorow", repeated words such as "The The", subject-verb agreement ("He don't"), a/an, their/they're/there, its/it's and your/you're mix-ups, and "could of". Names, acronyms, code identifiers and British spellings are left alone.
The Free plan returns the modified flag, the error count and the fully corrected text. Paid plans also receive the list of individual corrections: the rule each error broke, a readable message, the character positions where it starts and ends, and the replacement suggestions, which is what you need to underline errors in an editor and let the writer choose.
Grammar Check sends your text to a helper service built on harper-core 3, the Rust library behind the open-source Harper grammar checker, with an APIVerve layer on top that tunes it for automatic correction. Leading and trailing whitespace is trimmed first; line breaks inside the text are kept. An empty string returns a 400 error, and an input the checker service rejects also returns a 400 rather than a 500.
The text is parsed as Markdown, so inline code, links and URLs are not checked. The English variant is detected from the spelling the writer already uses and returned in dialect; British, Canadian, Australian and Indian spellings such as colour or theatre are not changed to American ones. Harper's grammar rules then run over the text, covering subject-verb agreement, a/an, their/they're/there, its/it's, your/you're, could of, repeated words, sentence capitalisation and several hundred common word-choice mistakes. Wording and style advice (shorter phrasings, en dashes and similar preferences) is not reported, because applying it automatically would rewrite correct text.
Spelling suggestions are ranked by how people actually mistype: swapped letters, a missing or extra double letter, a wrong vowel, a neighbouring key and words that sound alike count as smaller mistakes than arbitrary edits, and common words rank ahead of rare ones. A word typed in lowercase is never corrected to a proper noun, and the case you typed is kept, so TOMOROW becomes TOMORROW. Capitalised words in the middle of a sentence are treated as names and left alone unless they are one slip away from a known place or name. Acronyms, words with digits, camelCase identifiers and common technical terms such as JSON, OAuth or npm are not flagged.
errorCount is the number of reported problems and modified is true when there is at least one. corrected is built by applying the first suggestion of every problem, working from the end of the text backwards so earlier offsets stay valid; overlapping problems are reduced to one first, so every correction applies cleanly.
Each entry in corrections carries rule (the kind of problem, for example Spelling, Agreement, Repetition, Capitalization or Word Choice), message, position.start and position.end as character offsets into the trimmed text, and suggestions, the replacement strings for that span, best first. An empty-string suggestion means delete the span. Offsets count characters, not bytes, so they line up with JavaScript string indexes for most text. On the Free plan corrections is null and only the summary fields are returned.
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
Same data, same APIVerve account, same credit balance — one key works on all of them.
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
| Parameter | Type | Example | Description |
|---|---|---|---|
textRequired | string | This is a sample text with a grammatical error. | The English text you want to check for grammatical and spelling errors length 0-50000 |
curl -X POST "https://api.apiverve.com/v1/grammarcheck" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"The the pig snorted when I saw it on the barn gate. I was a little mad becuase it woke up my pupppppy"}'Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"modified": true,
"corrected": "The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy",
"errorCount": 3,
"dialect": "American",
"corrections": [
{
"rule": "Repetition",
"message": "Did you mean to repeat this word?",
"position": {
"start": 0,
"end": 7
},
"suggestions": [
"The"
]
},
{
"rule": "Spelling",
"message": "Did you mean `because`?",
"position": {
"start": 71,
"end": 78
},
"suggestions": [
"because"
]
},
{
"rule": "Spelling",
"message": "Did you mean `puppy`?",
"position": {
"start": 93,
"end": 101
},
"suggestions": [
"puppy",
"puppetry"
]
}
]
}
}
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
modified | boolean | true | Indicates whether any grammar or spelling errors were found |
corrected | string | "The pig snorted when I saw it on the barn gate. I was a little mad because it woke up my puppy" | The text with grammar and spelling corrections applied |
errorCount | number | 3 | Total number of errors found in the text |
dialect | string | "American" | The English variant the text was checked against, detected from its spelling: American, British, Canadian, Australian or Indian |
correctionsPremium | array[3] | Array of corrections with details about each error | |
rulePremium | string | "Repetition" | The kind of problem found, such as Spelling, Agreement, Repetition, Capitalization or Word Choice |
messagePremium | string | "Did you mean to repeat this word?" | Description of the error |
positionPremium | object | {...} | Start and end position of the error in the text |
startPremium | number | 0 | Character offset where the flagged text begins |
endPremium | number | 7 | Character offset where the flagged text ends |
suggestionsPremium | array | [The] | Replacement text for the flagged span, best first. An empty string means the span should be deleted |
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Grammar Check calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 10 | Free |
| Starter | $29.99 | 200,000 | 10,000 | $3.00 |
| Pro | $99.99 | 1,000,000 | 50,000 | $2.00 |
| Mega | $299.99 | 4,000,000 | 200,000 | $1.50 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
No SDK to install — this is a plain HTTPS call to /v1/grammarcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/grammarcheck" \
-H "x-api-key: YOUR_API_KEY"Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Node.js SDK, then call the Grammar Check API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/grammarcheckconst res = await fetch("https://api.apiverve.com/v1/grammarcheck", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the Python SDK, then call the Grammar Check API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-grammarcheckimport requests
res = requests.get(
"https://api.apiverve.com/v1/grammarcheck",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Install the C# / .NET SDK, then call the Grammar Check API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.GrammarCheckusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/grammarcheck");
Console.WriteLine(json);Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/grammarcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/grammarcheck", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/grammarcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/grammarcheck");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
No SDK to install — this is a plain HTTPS call to /v1/grammarcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/grammarcheck")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyOnly the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Drop an interactive Grammar Check form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Grammar Check API.
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read
7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read