Is a word plural or singular?
API · /inflector-api
Inflector API
English word inflection as an API. Pluralize or singularize any word — correctly handling the irregulars that trip up naive code (person ↔ people, cactus ↔ cacti, goose ↔ geese, analysis ↔ analyses, and uncountables like sheep and series). Get count-aware inflection ("1 item" vs "3 items", optionally with the number included), and check whether a given word is already singular or plural. Everything is computed locally, so it is instant and always available. Ideal for ORMs and code generators, REST resource naming, UI labels and notifications ("3 result(s)"), search and autocomplete, and any app that turns counts into correct grammar. For case styles and URL slugs, use the Text API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 70 ms
- Server probes · 24h
- Subscribers
- 4,274
- active
- Total calls
- 100
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 18,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 18,000 calls/month
- 2 req/sec
- Pluralize, singularize, inflect, check
- No credit card
Starter
€2.10 /month
- 245,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 245k calls/month
- 8 req/sec
- Count-aware inflection
- Email support
Pro
€7.90 /month
- 960,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 960k calls/month
- 20 req/sec
- ORMs & code generators
- Priority support
Mega
€27.10 /month
- 3,950,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 3.95M calls/month
- 50 req/sec
- High-traffic apps
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Grammar API
Catch spelling mistakes in six languages — English, German, Spanish, French, Portuguese and Dutch — and get English style and grammar suggestions in one call. Spelling errors come with their position in the text and a ranked list of corrections; style suggestions flag repeated words, weasel words, passive voice, wordiness, clichés and more. A combined check returns spelling and style together (sorted by position), a spelling-only endpoint covers all six languages, a single-word endpoint returns corrections for one word, and a languages endpoint lists what is supported. Every endpoint takes text via the query string or the request body and returns lean JSON. Pure server-side computation (Hunspell dictionaries + write-good, no third-party upstream, no LLM cost), so responses are instant and always available. Ideal for editors and CMSs, form and comment validation, chat and email tools, and writing assistants.
api.oanor.com/grammar-api
Keyboard Layout API
Re-map text between keyboard layouts — the fix for text typed with the keyboard set to the wrong layout. The remap endpoint takes text, a source layout and a target layout, and rewrites each character to the one produced by the same physical key on the other layout. So text accidentally typed on a Dvorak-configured keyboard while you meant QWERTY (or the reverse) is recovered exactly, and because the mapping is position-preserving it round-trips perfectly. It supports QWERTY (US), Dvorak and Colemak, including the shifted symbols, and leaves characters that are not on a remappable key (spaces and accents) untouched. The layouts endpoint returns the full key map for each layout. Everything is computed locally and deterministically, so it is instant and private. Ideal for fixing wrong-layout typing, building text editors and IME tools, layout-learning aids, and cross-layout search. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This remaps between keyboard layouts; for classical ciphers (Caesar, ROT13, Morse) use a cipher API.
api.oanor.com/keyboardlayout-api
Entropy API
Measure the information content of text. The analyze endpoint computes the Shannon entropy in bits per symbol, the total information in bits and bytes, the maximum possible entropy for the alphabet that was actually used, and a normalized 0–1 score that says how uniform (random-looking) the distribution is — over Unicode code points or raw UTF-8 bytes. The frequency endpoint returns the full character-frequency distribution, most common symbol first, with counts and percentages, showing control characters escaped and bytes as hex. It is exact, deterministic and runs entirely locally with no network calls, so it is instant and private. Ideal for randomness and password-quality checks, estimating how compressible data is, language and classical-cipher analysis, spotting low-variety or repetitive input, and feature extraction for text classification. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This measures information content; for password-strength scoring use a password API, for number statistics use a statistics API, and for grapheme/character counts use a text-segmentation API.
api.oanor.com/entropy-api
N-gram API
Generate n-grams from text, with frequency counts — entirely locally. The ngrams endpoint breaks text into contiguous sequences of n tokens and returns each distinct n-gram with how often it occurs, ranked by frequency: word n-grams (unigrams, bigrams, trigrams and beyond) for phrase and collocation analysis, or character n-grams (shingles) for fuzzy matching, language detection and indexing. The range endpoint produces every size from a minimum to a maximum in a single call (for example 1–3 grams), which is exactly what you need to build feature vectors. Choose word or character mode, whether to lower-case first, and a top-N limit to keep only the most frequent. Word tokenization is Unicode-aware and keeps internal apostrophes and hyphens (don't, well-known) as single tokens. Everything runs locally and deterministically, so it is fast and private. Ideal for text mining and NLP feature extraction, language modelling and autocomplete, search indexing and shingling, plagiarism and similarity detection, and keyword and collocation analysis. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This produces n-grams and counts; for extractive summaries and keywords use a summarize API and for grapheme/character counting use a text-segmentation API.
api.oanor.com/ngram-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Inflector API?
What's the rate limit for Inflector API?
How much does Inflector API cost?
Can I cancel my subscription anytime?
Is Inflector API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/inflector-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/inflector-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/inflector-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/inflector-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.