Title-case a heading
API · /titlecase-api
Title Case API
healthy
3,484 Subscribers
Convert a heading to proper headline (title) case the way editors do — not a naive capitalise-every-word. It capitalises the first and last words and all the major words, while keeping articles (a, an, the), coordinating conjunctions (and, but, or…) and prepositions lowercase, and always capitalises the word right after a colon. Choose AP style (lowercases short prepositions, capitalises longer ones) or Chicago style (lowercases prepositions of any length). Hyphenated compounds such as well-known and state-of-the-art are handled correctly. Perfect for article and blog titles, headings, SEO meta titles, product and section names, and CMS tooling. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Distinct from a plain title/sentence case converter, which capitalises every word.
api.oanor.com/titlecase-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 89 ms
- Server probes · 24h
- Subscribers
- 3,484
- active
- Total calls
- 39
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 1,175 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 1,175 calls/month
- 2 req/sec
- AP + Chicago
- No credit card
Starter
€2.15 /month
- 10,150 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 10.15k calls/month
- 8 req/sec
- Hyphen + colon handling
- Email support
Pro
€22.05 /month
- 152,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 152.5k calls/month
- 20 req/sec
- CMS / SEO pipelines
- Priority support
Mega
€60.05 /month
- 805,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 805k calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
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
Emoji Strip API
Strip, extract and count emoji in any text. The strip endpoint removes every emoji from a string — or replaces each one with a marker you choose — and gets multi-code-point emoji right: ZWJ sequences like the family 👩👩👧👦, skin-tone modifiers (👍🏽), country flags (🇩🇪), keycaps (1️⃣) and variation selectors all count as a single emoji, so nothing is left half-deleted. The extract endpoint lists every emoji it finds with its position in the text and returns per-emoji and unique counts, ideal for analytics and moderation. A bare ©, ® or ™ is deliberately left alone unless it carries an emoji variation selector, and plain digits are never touched. Perfect for cleaning user input before search indexing or storage, sanitising usernames and display names, moderation and analytics, and preparing text for systems that choke on emoji. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This cleans and extracts emoji from text; to look an emoji up by name or shortcode use an emoji database API, and to count graphemes use a text-segmentation API.
api.oanor.com/emojistrip-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Title Case API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Title Case API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Title Case API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Title Case API cost?
Title Case API has a free tier with 100 calls / month. Paid plans start at €2.15 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Title Case API GDPR-compliant?
All requests to Title Case API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
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/titlecase-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/titlecase-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/titlecase-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/titlecase-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
📌 Pinned
🔒 Locked
·
·
·
-
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.