Extract words ending with a suffix
Ask for words ending in ing and "The running fox is jumping, hopping, and singing while the dog is sleeping" gives running, jumping, hopping, singing and sleeping: 5 of 13 words, in order. No regular expression needed. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Suffix
- ing
- Words
- running, jumping, hopping, singing, sleeping
- Quantity
- 5
- Unique words
- running, jumping, hopping, singing, sleeping
- Unique count
- 5
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. 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.
What counts as a word ending and how the list is built
A word ending, for this extract-words-ending-with tool, is any token whose last characters match the suffix you chose, so running matches ing, nation matches tion, quickly matches ly, and moonlight matches ight. Tokens are contiguous runs of Unicode letters or digits, optionally joined by an internal apostrophe or hyphen, so well-being, O'Brien, and pre-owned stay single words instead of splitting on punctuation. Everything else—spaces, commas, periods, quotes, slashes, and emoji—acts as a boundary.
Matching is suffix-based, not phonetic: the letters at the end of the token must equal the suffix, without a pronunciation dictionary, stress marks, or syllable count. When case-insensitive mode is on (the default), Running and running both match the suffix ING, and uniqueness folds case while preserving the first spelling you typed. Prefer this landing when the search intent is extract words ending with, find words that end with a suffix, list rhyming endings, or filter a word list by grammar ending such as ed, ly, tion, or ness.
Do not use it for full rhyme-scheme analysis with phonemes and meter—that is a different product—or for listing every unique word regardless of ending, extracting capitalized names, converting case, or stemming lemmas.
What you can do with it
Rhyme banks for poets and lyricists
Paste a draft stanza, set suffix to ight or ation, and collect every matching word in order before a manual sound check.
Grammar-ending drills for teachers
Teachers extract words ending with ed, ly, or ing from a reading passage to build inflection drills and word-class lists.
FAQ
Are repeated words listed more than once?
Yes. The main list keeps every match in reading order, so a rhyme used twice in a stanza appears twice. A second list keeps each distinct word once, in the spelling it first had, for a clean rhyme bank.
Does it find words that rhyme by sound?
No. It compares letters only: the end of the word must equal the suffix you typed. There is no pronunciation dictionary, stress or syllable count, so check the sound of each match yourself.
Does uppercase matter?
Not by default: Running and running both match ING, and repeats are spotted regardless of case. With the strict option on, the ending must match exactly, so ED no longer catches walked.
Can the ending contain a space or several words?
No. An ending is the tail of a single word, so a suffix with a space inside is rejected. Spaces typed before or after it are simply trimmed away.
Related tools
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. |
Technical notes
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.
What counts as a word ending and how the list is built
The scan walks left to right and appends every matching token to the words array, keeping duplicates when the same rhyme or inflection appears twice in a stanza; a separate unique_words array keeps only the first surface form of each distinct token so you can build a clean rhyme bank, grammar list, or filtered vocabulary set. When case-insensitive mode is off, the ending must match exactly, so ED does not catch walked and ing does not catch SINGING. total_tokens reports how many words were seen before the suffix filter, which helps you gauge how dense the matching subset is relative to the full passage.
Input contract, empty rejection, and reading the response fields
A suffix that contains whitespace is also rejected, because an ending is a single token tail, not a phrase. Because the algorithm is pure string logic, continuous-integration tests can pin the full object. Source text follows the same retention rules as other KIT parse items. POST a JSON body with the required string field text set to the non-empty sample you want scanned and the required string field suffix set to the ending you want to match. Aliases input, value, s, content, and body are accepted for the source text when older clients or form generators use those names; aliases ending, ends_with, and ending_with are accepted for the suffix. Missing text, a non-string text value, a zero-length text string, a missing suffix, a non-string suffix, or a suffix that is empty after trimming all raise invalid_input with a message that names the problem, and those failures are not charged on the prepaid API. Whitespace-only text that is still non-empty is allowed: it may yield zero matching tokens and empty words and unique_words arrays, which is a valid success shape when the passage has no words that finish with the chosen ending. Optional case_insensitive defaults to true; aliases ignore_case, ci, and casefold are accepted. On success the response includes words as the ordered list of matching tokens with duplicates preserved; count as that array length; unique_words as first-seen distinct matches; unique_count as that length; total_tokens as the full token count before filtering; suffix echoing the trimmed ending used; case_insensitive echoing the mode; original echoing the exact input for UI tables; and method always extract_words_ending so downstream code can branch without sniffing shapes. Use words when you care about frequency of an ending; use unique_words when you only need a set of candidate rhymes or inflected forms. Keep payloads to ordinary document sizes suitable for a Worker isolate rather than multi-megabyte dumps; this product is a text utility, not a bulk warehouse.
API usage, pricing, workflows, and practical limits
Call the free in-browser extract words ending with tool when you need a quick rhyme shortlist, a grammar-ending drill, or a filtered word bank from a poem, lesson, novel chapter, or marketing brief without writing a regex in every language. Do not expect phonetic rhyme scoring, syllable counts, stress marks, language detection, or stemming—those are separate problems with separate SEO terms. Authors shipping SDKs can document text and suffix as the required fields, show a success example with an ing or tion ending, and show an empty-string error example so integrators see both sides of the contract. Use the prepaid KIT API when a CMS, content pipeline, tutoring app, research notebook, crossword helper, or mobile client needs the same contract under balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request. A typical workflow pastes a stanza, sets suffix to ight or ation, lists matching words, then reviews unique_words for a clean rhyme bank before a manual sound check. Pair this endpoint with unique-word extractors or frequency counters when the next step is vocabulary banks or style audits, but keep extract words ending with as its own landing so the suffix-filter and rhyme-finding intent is not mixed with capitalized-word lists or keyword extraction.
Integration use cases
CI fixtures for tokenizer pipelines
Build scripts pin suffix-filter golden outputs so Unicode, apostrophe, hyphen, and case-fold regressions fail continuous integration immediately.
Technical questions
How do I extract words that end with a suffix?
Send JSON with text set to a non-empty string and suffix set to the ending you want, such as ing or tion. The response words array lists each match in order; unique_words lists first-seen forms only.
Is matching case-sensitive?
By default no: case_insensitive is true, so Running matches suffix ING. Set case_insensitive to false when the ending must match exactly.
Are duplicate words listed more than once?
Yes in words, so you can see how often an ending appears. unique_words keeps each distinct surface form only the first time it appears.
What happens if text or suffix is empty?
The request fails with invalid_input. Empty text and empty suffix are not allowed; validation failures are not charged on the prepaid API.
What does extract words ending with cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.