Count occurrences of a word
Count how many times a specific word appears in a passage without accidentally counting it inside longer words.
Run — free
This whole-word counter is useful for writers checking repetition, editors tracking required terminology, teachers reviewing student work, and developers validating generated content. Matching is case-insensitive by default, so Word and word belong to the same count, while an optional case-sensitive mode keeps them separate. Unicode letters and digits are supported, including words with internal apostrophes. The result also reports the total number of recognized words, making it easy to understand the count in context. Processing is deterministic and local in the free browser tool, while API requests cost $0.002 per successful item.
How to use it
Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.
Check your inputs
Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.
Use it again or automate it
Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.
What you can do with it
Get an answer now
Enter one set of values and see the result without building a spreadsheet or script.
Compare scenarios
Change one value at a time and rerun the calculation to understand what affects the result.
Automate repeated work
Use the API when the same calculation needs to run inside your product or workflow.
FAQ
How do I use this capability?
Complete the fields above and run it on this page. The form highlights anything that needs attention.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/str/count-word-occurrences \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Blue skies look blue, but blueberry is not blue.","word":"blue"}'const res = await fetch("https://api.kit.forhosting.com/str/count-word-occurrences", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "Blue skies look blue, but blueberry is not blue.",
"word": "blue"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/count-word-occurrences",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "Blue skies look blue, but blueberry is not blue.",
"word": "blue"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/count-word-occurrences", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"Blue skies look blue, but blueberry is not blue.","word":"blue"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"Blue skies look blue, but blueberry is not blue.","word":"blue"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/count-word-occurrences", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "Blue skies look blue, but blueberry is not blue.",
"word": "blue"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.count_word_occurrences",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_chars | 100000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |