Proper-case a name
API · /name-api
Name API
healthy
4,104 Subscribers
Clean up and parse personal names. The case endpoint applies proper name-casing that ordinary title-casing gets wrong — McDonald, MacLeod, O'Brien, D'Angelo, hyphenated double-barrelled names, lower-case particles (van, von, de, la, der) and Roman-numeral suffixes (II, III, IV). The parse endpoint splits a full name into salutation, first, middle and last name and suffix, and also returns a properly-cased version of each part. Perfect for tidying user sign-ups, CRM and mailing lists, deduplicating contacts, formatting names on documents and normalising imported data. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Parsing is tuned for Western (given-name-first) order. Distinct from baby-name popularity data and locale display-name lookups.
api.oanor.com/name-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 94 ms
- Server probes · 24h
- Subscribers
- 4,104
- active
- Total calls
- 45
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 940 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 940 calls/month
- 2 req/sec
- Case + parse
- No credit card
Starter
€2.00 /month
- 7,900 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 7.9k calls/month
- 8 req/sec
- Particles + suffixes + Mc/Mac
- Email support
Pro
€20.80 /month
- 134,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 134k calls/month
- 20 req/sec
- CRM / data-cleaning pipelines
- Priority support
Mega
€56.80 /month
- 690,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 690k calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Baby Names API
US given-name popularity from 1880 to 2008 as an API — the top 1,000 names per year for each sex (SSA-derived dataset, 6,782 names). Pull a name's full popularity trend (e.g. Emma → girls: rank #1 in 2008, peaked again in 1881), get the top names for any year (e.g. 1990 → Jessica, Ashley, Brittany), or search names by prefix/substring. Each data point carries the year, the share of births (percent and per-million) and the rank. Ideal for name-trend visualisations, baby-name apps, nostalgia/genealogy tools and data journalism.
api.oanor.com/babynames-api
Name Insights API
Enrich a first name with predicted gender, age and nationality — with confidence probabilities and an optional country bias for higher accuracy. One combined call returns all three. Ideal for CRM enrichment, personalization, form pre-fill, audience analytics and demographic segmentation.
api.oanor.com/nameinsights-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
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Name API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Name API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Name 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 Name API cost?
Name API has a free tier with 100 calls / month. Paid plans start at €2.00 / 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 Name API GDPR-compliant?
All requests to Name 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/name-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/name-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/name-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/name-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.