Extract words ending with a suffix
Extracting words that end with a chosen suffix is a practical text utility with a clear product promise: take a non-empty passage, pick the ending you care about, and list every word that finishes with that suffix so you can hunt rhymes, study grammar endings, and filter a word bank without writing a regular expression.
Run — free
Poets, teachers, linguists, crossword solvers, and automation scripts all hit the same search intent when they type extract words ending with, find words that end with, or list words ending with a suffix. This capability uses a deterministic Unicode-aware tokenizer and a suffix match—no language model, no network round-trip, and no random sampling—so the free browser widget and the prepaid API always agree byte-for-byte. Empty text or an empty suffix is rejected with invalid input so callers never store hollow payloads by accident. Successful API calls bill at the published $0.002 base price per item; validation failures are not charged.
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/extract-words-ending \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"The running fox is jumping, hopping, and singing while the dog is sleeping.","suffix":"ing"}'const res = await fetch("https://api.kit.forhosting.com/str/extract-words-ending", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "The running fox is jumping, hopping, and singing while the dog is sleeping.",
"suffix": "ing"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/extract-words-ending",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "The running fox is jumping, hopping, and singing while the dog is sleeping.",
"suffix": "ing"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/extract-words-ending", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"The running fox is jumping, hopping, and singing while the dog is sleeping.","suffix":"ing"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"The running fox is jumping, hopping, and singing while the dog is sleeping.","suffix":"ing"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/extract-words-ending", 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": "The running fox is jumping, hopping, and singing while the dog is sleeping.",
"suffix": "ing"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.extract_words_ending",
"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.
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. |