Kurdish data for AI training, collected to your brief
Kurdish data from IndecalAI is collected or reviewed by a native Kurdish speaker, not pulled from an existing archive. We work with speakers across the Middle East and Central Asia, where a formal written register and everyday speech can diverge sharply, matched to your brief and checked before delivery.
What Kurdish data can we produce?
Kurdish data from IndecalAI is speech, text, conversational and translation data collected or reviewed by a Kurdish speaker for your brief, not pulled from an existing archive.
A formal written register and everyday spoken language can differ sharply in this region, so we ask upfront whether you need the standard written form, a regional spoken variety, or both.
This sits across several of our services depending on what you need: data collection for raw speech or text, conversational AI data for dialogue, and translation and localization for converting between Kurdish and another language.
Translation projects often pair this language with English or another regional language. See translation and localization for that scope.
Kurdish data at a glance
- Data types
- Speech, text, conversational, translation
- Services
- Data collection, Translation
- Who works on it
- Contributors from our network of 30,000+ people worldwide, matched to your brief.
- Review
- A review pass before anything is delivered.
- Your data
- NDA first, used only for the agreed scope, returned or deleted when you ask.
- First step
- A small free sample before you commit.
What to know about Kurdish before you brief it
Kurdish is spoken across Turkey, Iraq, Iran and Syria, and it is better described as a group of related varieties than a single standard. Each variety has its own community, media and writing habits.
The two main varieties are Kurmanji, mostly written in Latin letters, and Sorani, written in an Arabic-based script that runs right to left. Speakers of one often cannot easily follow the other, so a brief must name the variety, not simply say Kurdish. The country matters too, because vocabulary and the languages Kurdish speakers mix with, such as Turkish, Arabic or Persian, differ from place to place.
Languages that sit close to Kurdish in script, family or region: Persian data, Turkish data, Pashto data, Arabic data, Azerbaijani data and Armenian data.
Deciding what to specify for any language? The guide to speech data collection covers the choices that apply across languages, and the one on transcription for AI and for people covers how speech becomes text.
Kurdish at a glance
- Language family
- Indo-European (Iranian)
- Script
- Latin for Kurmanji, a Perso-Arabic script for Sorani (right to left)
- Spoken mainly in
- Turkey, Iraq, Iran and Syria
- Name it in a brief
- Kurmanji (Northern Kurdish), Sorani (Central Kurdish), Southern Kurdish
- Its own name
- Kurdî
Four ways to request Kurdish data
Each links to the service that runs it, with its full scope and process.
Kurdish speech data
Recorded speech in Kurdish: calls, prompts and voice bot utterances, in either the standard written register or a regional spoken variety, to your brief.
Kurdish text data
Written Kurdish: messages, reviews, tickets or chat logs, written or labeled by people who read it natively.
Kurdish conversational data
Scripted or spontaneous Kurdish dialogue for voice bots and support agents, in the formal or everyday register your brief calls for.
Kurdish translation
Human-verified translation between Kurdish and another language, covering both formal and everyday registers.
What to put in a Kurdish brief
Four things worth deciding before contributors start, so the first sample already looks right.
Region or dialect
Kurdish is spoken mainly in Turkey, Iraq, Iran and Syria. Worth naming in a brief: Kurmanji (Northern Kurdish), Sorani (Central Kurdish), Southern Kurdish. Tell us the region or community you're targeting so contributors are matched to the right one.
Script or transliteration
Script for Kurdish: Latin for Kurmanji, a Perso-Arabic script for Sorani (right to left). Say whether you want the native script, a transliterated version, or both, especially if your downstream system only reads one.
Data type mix
Speech, text, conversational and translation can be requested together or on their own. Tell us the mix your model needs.
Volume and timeline
A rough sense of how much data and how soon lets us staff the right number of contributors from the start.
From your brief to reviewed Kurdish data
One named contact owns the project from scoping to the last file.
Brief
You tell us the data type, the Kurdish variety or region and roughly how much you need.
NDA and scope
We sign an NDA before any data moves, then agree the scope with you.
Free sample
We produce a small sample free, so you can check it before you commit.
Production
Contributors from our network work in our own tools, to the brief you set.
Review
A review pass runs before anything is delivered.
Delivery
The data comes to you, or moves on to another service with us.
Where Kurdish data ends up
Common jobs for Kurdish data. They're examples of the work, not a client list.
Voice bots and IVR
Recorded Kurdish prompts and calls teach a voice bot to recognize how people actually speak, not just how a script reads.
Support chat and tickets
Everyday Kurdish messages, written in the domain you work in, give a chat assistant real phrasing to learn from.
Content moderation and sentiment
Labeled Kurdish posts, reviews and messages teach a model to read tone and intent correctly in this language.
Localizing a product
Translating prompts, UI copy and training data into Kurdish so a product reads like it was written for that market, not machine-translated.
Off-the-shelf Kurdish data, or built to your brief?
We hold around 35,000 hours of off-the-shelf speech, prompts and conversations already collected across our network. We can't promise Kurdish is in that pool until you ask, but it's worth checking before you commission a fresh collection. Here's how the two paths compare.
| Topic | A typical off-the-shelf dataset | Kurdish data with us |
|---|---|---|
| Already collected? | No way to know until you've already paid for it | We check our ~35,000-hour speech and conversation pool first and tell you honestly either way |
| Fit to your brief | Built for whoever bought it first, not your exact region, register or use case | Collected or reviewed to the region, script and format you specify |
| Who else has it | The same files can be sold to more than one buyer | Scoped to your engagement, never resold for unrelated projects |
| Checking the fit | You find out after you've already paid for it | A small free sample first, so you check it before committing to volume |
Kurdish data terms, in plain words
General definitions. They describe the field, not a claim about us.
Where Kurdish data fits
Kurdish is one of 100 languages on our languages directory. You can also browse every category on the datasets hub.
Questions about Kurdish data
The datasets FAQ covers questions that apply across every category.
Do you support Kurdish?
Yes. Kurdish is one of 100 languages in this directory, part of our wider language coverage worldwide, including deep Indian language coverage. Tell us the regional variety you need.
Do you already have any Kurdish data collected?
Maybe. We hold around 35,000 hours of off-the-shelf speech, prompts and conversations across our network, but we can't promise Kurdish is in that pool until you ask. It costs nothing to check before you commission a fresh collection.
Can you mix regional varieties of Kurdish in one project?
Yes. Tell us the mix of regions or dialects you need and we'll match contributors from our network to that brief.
Which data types are available in Kurdish?
Speech, text, conversational data and translation to or from Kurdish. Image and video categories don't depend on language, so Kurdish speakers can also appear in those briefs on request.
Is a sample available before we commit?
Yes, a small free sample first.
Can this run alongside other languages in the same project?
Yes. Many engagements mix languages, domains and data types under one brief and one named contact, using our network of 30,000+ people across 150+ projects delivered so far.
What counts as a regional variety of Kurdish?
A version of the language tied to a place or community, which can differ in vocabulary, pronunciation, formality or script from another region's variety. Name the region in your brief if it matters for your use case.
Can you handle Kurdish in its native script?
Yes. Contributors work in the native script by default, with transliteration available if your project needs it instead.
Which variety of Kurdish should I ask for?
Ask for the one your users actually speak. Kurdish is spoken mainly in Turkey, Iraq, Iran and Syria, and the forms most worth naming in a brief are Kurmanji (Northern Kurdish), Sorani (Central Kurdish), Southern Kurdish. If you are unsure, describe your users and where they live, and your named contact will help you decide before collection starts.
How is Kurdish written, and does it matter for the data?
Kurdish data uses Latin for Kurmanji, a Perso-Arabic script for Sorani (right to left). The script and its encoding affect how a model reads the data, so say in the brief which one you need and whether a romanized or transliterated version is also required.
Request Kurdish data
Pick the data type, confirm Kurdish as the language and a rough volume, and send it. We'll produce a small sample free before you commit.
- Your named contact replies within one business day.
- We sign an NDA before any data changes hands.
- We produce your free sample, then agree the full scope.
This opens your email app with the brief filled in. Nothing is sent until you press send. You can also use the contact page.