For the complete documentation index, see llms.txt.
One-, two- and three-word keyword density with stop-word filtering and word counts.
One POST adds Keyword Density Checker to your app, site, workflow, or agent — formula, validation, edge cases, and docs already handled.
prefer a UI? Open the Keyword Density Checker on miniwebtool.com →
POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/run
| Field | Type | Req. |
|---|---|---|
text
content to analyse
|
str |
✓ |
exclude_stop_words
yes | no
|
str |
— |
min_length
minimum word length
|
int |
— |
top_n
how many phrases to return per group
|
int |
— |
524288 bytes.no_body_logs{
"request_id": "01K...",
"tool": "keyword-density-checker",
"tool_version": "2026-04-22",
"credits_used": 1,
"result": { ... }
}
1,000 free calls/mo · no card · key arrives by email
curl -X POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/run \
-H 'Authorization: Bearer mwt_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"text":"SEO content optimization improves SEO rankings. Good SEO content wins.","exclude_stop_words":"yes","min_length":3,"top_n":5}'
import requests
resp = requests.post(
'https://api.miniwebtool.com/v1/tools/keyword-density-checker/run',
headers={'Authorization': 'Bearer mwt_live_YOUR_KEY'},
json={'text': 'SEO content optimization improves SEO rankings. Good SEO content wins.', 'exclude_stop_words': 'yes', 'min_length': 3, 'top_n': 5},
)
resp.raise_for_status()
data = resp.json()
print(data)
const resp = await fetch(
'https://api.miniwebtool.com/v1/tools/keyword-density-checker/run',
{
method: 'POST',
headers: {
'Authorization': 'Bearer mwt_live_YOUR_KEY',
'Content-Type': 'application/json',
},
body: JSON.stringify({"text":"SEO content optimization improves SEO rankings. Good SEO content wins.","exclude_stop_words":"yes","min_length":3,"top_n":5}),
}
);
const data = await resp.json();
console.log(data);
<?php
$ch = curl_init('https://api.miniwebtool.com/v1/tools/keyword-density-checker/run');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer mwt_live_YOUR_KEY',
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => json_encode([
'text' => 'SEO content optimization improves SEO rankings. Good SEO content wins.',
'exclude_stop_words' => 'yes',
'min_length' => 3,
'top_n' => 5
]),
]);
$resp = curl_exec($ch);
curl_close($ch);
print_r(json_decode($resp, true));
require 'net/http'
require 'json'
require 'uri'
uri = URI('https://api.miniwebtool.com/v1/tools/keyword-density-checker/run')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = (uri.scheme == 'https')
req = Net::HTTP::Post.new(uri)
req['Authorization'] = 'Bearer mwt_live_YOUR_KEY'
req['Content-Type'] = 'application/json'
req.body = {
'text' => 'SEO content optimization improves SEO rankings. Good SEO content wins.',
'exclude_stop_words' => 'yes',
'min_length' => 3,
'top_n' => 5
}.to_json
resp = http.request(req)
puts JSON.parse(resp.body).inspect
package main
import (
"bytes"
"encoding/json"
"fmt"
"io"
"net/http"
)
func main() {
body, _ := json.Marshal(map[string]interface{}{
"text": "SEO content optimization improves SEO rankings. Good SEO content wins.",
"exclude_stop_words": "yes",
"min_length": 3,
"top_n": 5,
})
req, _ := http.NewRequest("POST", "https://api.miniwebtool.com/v1/tools/keyword-density-checker/run", bytes.NewReader(body))
req.Header.Set("Authorization", "Bearer mwt_live_YOUR_KEY")
req.Header.Set("Content-Type", "application/json")
resp, err := http.DefaultClient.Do(req)
if err != nil { panic(err) }
defer resp.Body.Close()
out, _ := io.ReadAll(resp.Body)
fmt.Println(string(out))
}
import java.net.URI;
import java.net.http.*;
var client = HttpClient.newHttpClient();
var req = HttpRequest.newBuilder()
.uri(URI.create("https://api.miniwebtool.com/v1/tools/keyword-density-checker/run"))
.header("Authorization", "Bearer mwt_live_YOUR_KEY")
.header("Content-Type", "application/json")
.POST(HttpRequest.BodyPublishers.ofString("{\"text\":\"SEO content optimization improves SEO rankings. Good SEO content wins.\",\"exclude_stop_words\":\"yes\",\"min_length\":3,\"top_n\":5}"))
.build();
var resp = client.send(req, HttpResponse.BodyHandlers.ofString());
System.out.println(resp.body());
Copy this into Claude Code, Cursor, Codex, Aider or Cline. It carries the endpoint,
the full schema, a sample response, and the credit rules — so the agent wires
keyword-density-checker up correctly without draining your key.
POST /v1/tools/keyword-density-checker/dry-run, which validates
the request and returns the response shape for
0 credits. Only the final confirmation call is billed
(1 credit).
/tools/keyword-density-checker/prompt.md
(?variant=cursor / ?variant=mcp).
Integrate the MiniWebtool Keyword Density Checker API into this project.
## Your task
1. Read the reference below.
2. Ask me where this belongs in the codebase if it is not obvious.
3. Write the integration in the language and style of the surrounding code:
a small typed client function, errors handled, key read from the
environment (never hard-coded, never committed).
4. Verify with `/dry-run` first, then exactly one live call.
5. Show me the diff and the live result.
## Credit budget — follow these exactly
This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.
1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
payload for real and returns a sample result with the exact response shape.
Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
`application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
tool is deterministic, so the same input always returns the same output.
## The API
**Keyword Density Checker** — One-, two- and three-word keyword density with stop-word filtering and word counts.
- Live endpoint: `POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/run` — costs 1 credit
- Dry run: `POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/dry-run` — costs 0 credits, same auth and validation
- Auth: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
- Content type: `application/json`
- Tool version: `2026-04-22` (output shape is stable within a major version)
- Full machine-readable spec: `https://api.miniwebtool.com/v1/openapi.json`
### Request body
| field | type | required | notes |
|---|---|---|---|
| `text` | str | yes | content to analyse |
| `exclude_stop_words` | str | no | one of: yes, no — yes \| no (default `yes`) |
| `min_length` | int | no | minimum word length (default `3`) |
| `top_n` | int | no | how many phrases to return per group (default `10`) |
Example request body:
```json
{
"text": "SEO content optimization improves SEO rankings. Good SEO content wins.",
"exclude_stop_words": "yes",
"min_length": 3,
"top_n": 5
}
```
### Response envelope
```json
{
"request_id": "req_01H…",
"tool": "keyword-density-checker",
"tool_version": "2026-04-22",
"credits_used": 1,
"result": {
"total_words": 10,
"analyzed_words": 10,
"unique_words": 7,
"characters": 70,
"exclude_stop_words": "yes",
"min_word_length": 3,
"one_word": [
{
"phrase": "seo",
"count": 3,
"density_pct": 30.0
},
{
"phrase": "content",
"count": 2,
"density_pct": 20.0
},
{
"phrase": "optimization",
"count": 1,
"density_pct": 10.0
},
{
"phrase": "improves",
"count": 1,
"density_pct": 10.0
},
{
"phrase": "rankings",
"count": 1,
"density_pct": 10.0
}
],
"two_word": [
{
"phrase": "seo content",
"count": 2,
"density_pct": 22.222
},
{
"phrase": "content optimization",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "optimization improves",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "improves seo",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "seo rankings",
"count": 1,
"density_pct": 11.111
}
],
"three_word": [
{
"phrase": "seo content optimization",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "content optimization improves",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "optimization improves seo",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "improves seo rankings",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "seo rankings good",
"count": 1,
"density_pct": 12.5
}
],
"note": "Density is the share of analysed words, after stop-word and length filtering."
}
}
```
`result` holds the tool output. Errors come back as
`application/problem+json` with `type`, `title`, `status`, and `detail`.
### Getting a key
If `MINIWEBTOOL_API_KEY` is not already in the environment, stop and ask me for
one — do not sign up, scrape, or guess a key. Free keys: https://api.miniwebtool.com/dashboard/
Integrate the MiniWebtool Keyword Density Checker API into this project.
## Your task
1. Read the reference below.
2. Ask me where this belongs in the codebase if it is not obvious.
3. Write the integration in the language and style of the surrounding code:
a small typed client function, errors handled, key read from the
environment (never hard-coded, never committed).
4. Verify with `/dry-run` first, then exactly one live call.
5. Show me the diff and the live result.
## Credit budget — follow these exactly
This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.
1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
payload for real and returns a sample result with the exact response shape.
Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
`application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
tool is deterministic, so the same input always returns the same output.
## The API
**Keyword Density Checker** — One-, two- and three-word keyword density with stop-word filtering and word counts.
- Live endpoint: `POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/run` — costs 1 credit
- Dry run: `POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/dry-run` — costs 0 credits, same auth and validation
- Auth: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
- Content type: `application/json`
- Tool version: `2026-04-22` (output shape is stable within a major version)
- Full machine-readable spec: `https://api.miniwebtool.com/v1/openapi.json`
### Request body
| field | type | required | notes |
|---|---|---|---|
| `text` | str | yes | content to analyse |
| `exclude_stop_words` | str | no | one of: yes, no — yes \| no (default `yes`) |
| `min_length` | int | no | minimum word length (default `3`) |
| `top_n` | int | no | how many phrases to return per group (default `10`) |
Example request body:
```json
{
"text": "SEO content optimization improves SEO rankings. Good SEO content wins.",
"exclude_stop_words": "yes",
"min_length": 3,
"top_n": 5
}
```
### Response envelope
```json
{
"request_id": "req_01H…",
"tool": "keyword-density-checker",
"tool_version": "2026-04-22",
"credits_used": 1,
"result": {
"total_words": 10,
"analyzed_words": 10,
"unique_words": 7,
"characters": 70,
"exclude_stop_words": "yes",
"min_word_length": 3,
"one_word": [
{
"phrase": "seo",
"count": 3,
"density_pct": 30.0
},
{
"phrase": "content",
"count": 2,
"density_pct": 20.0
},
{
"phrase": "optimization",
"count": 1,
"density_pct": 10.0
},
{
"phrase": "improves",
"count": 1,
"density_pct": 10.0
},
{
"phrase": "rankings",
"count": 1,
"density_pct": 10.0
}
],
"two_word": [
{
"phrase": "seo content",
"count": 2,
"density_pct": 22.222
},
{
"phrase": "content optimization",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "optimization improves",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "improves seo",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "seo rankings",
"count": 1,
"density_pct": 11.111
}
],
"three_word": [
{
"phrase": "seo content optimization",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "content optimization improves",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "optimization improves seo",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "improves seo rankings",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "seo rankings good",
"count": 1,
"density_pct": 12.5
}
],
"note": "Density is the share of analysed words, after stop-word and length filtering."
}
}
```
`result` holds the tool output. Errors come back as
`application/problem+json` with `type`, `title`, `status`, and `detail`.
### Getting a key
If `MINIWEBTOOL_API_KEY` is not already in the environment, stop and ask me for
one — do not sign up, scrape, or guess a key. Free keys: https://api.miniwebtool.com/dashboard/
---
description: MiniWebtool Keyword Density Checker API — usage and credit budget
globs:
alwaysApply: false
---
# MiniWebtool Keyword Density Checker API
## The API
**Keyword Density Checker** — One-, two- and three-word keyword density with stop-word filtering and word counts.
- Live endpoint: `POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/run` — costs 1 credit
- Dry run: `POST https://api.miniwebtool.com/v1/tools/keyword-density-checker/dry-run` — costs 0 credits, same auth and validation
- Auth: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
- Content type: `application/json`
- Tool version: `2026-04-22` (output shape is stable within a major version)
- Full machine-readable spec: `https://api.miniwebtool.com/v1/openapi.json`
### Request body
| field | type | required | notes |
|---|---|---|---|
| `text` | str | yes | content to analyse |
| `exclude_stop_words` | str | no | one of: yes, no — yes \| no (default `yes`) |
| `min_length` | int | no | minimum word length (default `3`) |
| `top_n` | int | no | how many phrases to return per group (default `10`) |
Example request body:
```json
{
"text": "SEO content optimization improves SEO rankings. Good SEO content wins.",
"exclude_stop_words": "yes",
"min_length": 3,
"top_n": 5
}
```
### Response envelope
```json
{
"request_id": "req_01H…",
"tool": "keyword-density-checker",
"tool_version": "2026-04-22",
"credits_used": 1,
"result": {
"total_words": 10,
"analyzed_words": 10,
"unique_words": 7,
"characters": 70,
"exclude_stop_words": "yes",
"min_word_length": 3,
"one_word": [
{
"phrase": "seo",
"count": 3,
"density_pct": 30.0
},
{
"phrase": "content",
"count": 2,
"density_pct": 20.0
},
{
"phrase": "optimization",
"count": 1,
"density_pct": 10.0
},
{
"phrase": "improves",
"count": 1,
"density_pct": 10.0
},
{
"phrase": "rankings",
"count": 1,
"density_pct": 10.0
}
],
"two_word": [
{
"phrase": "seo content",
"count": 2,
"density_pct": 22.222
},
{
"phrase": "content optimization",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "optimization improves",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "improves seo",
"count": 1,
"density_pct": 11.111
},
{
"phrase": "seo rankings",
"count": 1,
"density_pct": 11.111
}
],
"three_word": [
{
"phrase": "seo content optimization",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "content optimization improves",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "optimization improves seo",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "improves seo rankings",
"count": 1,
"density_pct": 12.5
},
{
"phrase": "seo rankings good",
"count": 1,
"density_pct": 12.5
}
],
"note": "Density is the share of analysed words, after stop-word and length filtering."
}
}
```
`result` holds the tool output. Errors come back as
`application/problem+json` with `type`, `title`, `status`, and `detail`.
### Getting a key
If `MINIWEBTOOL_API_KEY` is not already in the environment, stop and ask me for
one — do not sign up, scrape, or guess a key. Free keys: https://api.miniwebtool.com/dashboard/
## Credit budget — follow these exactly
This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.
1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
payload for real and returns a sample result with the exact response shape.
Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
`application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
tool is deterministic, so the same input always returns the same output.
Add the MiniWebtool MCP server to this project, then use the
`keyword-density-checker` tool from it.
Server URL: https://api.miniwebtool.com/v1/mcp
Transport: HTTP (Streamable HTTP / JSON-RPC 2.0)
Auth header: `Authorization: Bearer <MINIWEBTOOL_API_KEY>`
Claude Code:
```bash
claude mcp add --transport http miniwebtool https://api.miniwebtool.com/v1/mcp \
--header "Authorization: Bearer $MINIWEBTOOL_API_KEY"
```
Or add it to the MCP config file your client uses:
```json
{
"mcpServers": {
"miniwebtool": {
"type": "http",
"url": "https://api.miniwebtool.com/v1/mcp",
"headers": { "Authorization": "Bearer ${MINIWEBTOOL_API_KEY}" }
}
}
}
```
Once connected, `tools/list` exposes `keyword-density-checker` with its JSON Schema, so you can
call it directly instead of writing an HTTP client.
## Credit budget — follow these exactly
This API is metered. A live call costs 1 credit; the free tier
includes 1,000 credits per month. Burning them during integration is the
single most common way to waste this key.
1. **Do all wiring against `/dry-run`, which costs 0 credits.** It validates the
payload for real and returns a sample result with the exact response shape.
Iterate there until your request builds and your parsing works.
2. **Make at most ONE live `/run` call** — a single end-to-end confirmation once
dry-run passes. Print the result, then stop.
3. **Never call the API from unit tests, examples, or a retry loop.** Assert
against the sample response captured from `/dry-run` instead.
4. **On 4xx, fix the payload — do not retry.** The error body is RFC 7807
`application/problem+json` and says exactly what is wrong.
5. **On 429, honour `Retry-After`** and back off; do not tighten the loop.
6. **Read `X-MWT-Credits-Remaining`** on every response. If it drops below 50,
stop making live calls and tell me.
7. If the integration needs repeated calls at runtime, **cache by input** — this
tool is deterministic, so the same input always returns the same output.
text, . See the Request body table above for the full schema.
https://api.miniwebtool.com/v1/tools/keyword-density-checker/run
Authorization: Bearer <key> and Content-Type: application/json. Copy-paste snippets in 7 languages are under Code examples.
{request_id, tool, tool_version, credits_used, result}. The typed output lives in result.
One-, two- and three-word keyword density with stop-word filtering and word counts. Use it to add this utility without rebuilding formulas, validation, examples, and documentation.
1 credit per successful call. Failed calls (validation errors, 5xx) don't bill.
Required fields: text. Full schema at /v1/openapi.json.
Yes — same input, same output, forever. Tool version 2026-04-22; output shape is stable within a major version.
Yes. Connect to https://api.miniwebtool.com/v1/mcp over the Model Context Protocol. The agent discovers `keyword-density-checker` with its JSON Schema automatically, so the model can plan while MiniWebtool handles the exact tool result.
JSON with a stable envelope: `{request_id, tool, tool_version, credits_used, result}`. Errors are RFC 7807 `application/problem+json`.
Every endpoint on this site is also exposed via the
Model Context Protocol at
https://api.miniwebtool.com/v1/mcp.
Claude, Cursor, and any MCP-capable agent can discover this tool
(keyword-density-checker)
and its JSON Schema automatically — no client codegen.
# List tools the agent can call
curl -s https://api.miniwebtool.com/v1/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \
| jq '.result.tools[] | select(.name=="keyword-density-checker")'