Written by people
Prompts, questions, answers and everyday messages, written by people in the languages and the domain you need.
For chat assistants, search and language models
Text data for AI is written language your model learns to read or write: prompts, questions, messages and reviews, paired with labels. People from our 30,000+ network write it in the languages and domain you need, and our annotators and translators label and translate it.
written · same request, three writers
intent: reschedule delivery
Move my blue kurta product delivery to Friday date at 6 pm time in Pune place.
labeledtranslated · reviewed
Text data for AI is written language paired with labels, like the intent behind a message or the names and dates in it, that a language model learns to read or write from. The text shows how people really write, and the labels tell the model what it means.
Good text data sounds like your users. The same request written by many people, in their own words, teaches a model far more than one tidy version repeated.
It usually needs a label set agreed up front, and in multilingual products it needs the same care in every language, scripts and spelling habits included.
Labels are only as useful as they are consistent, and our guide to data annotation quality shows what to look for before you trust a labeled set.
One customer request, from how people wrote it to how it reads in Hindi. Switch layers to see each stage. It's an example, and your layers are agreed with you.
The same request written by many people in their own words, so your model learns how users really phrase things.
The intent behind each message and the entities inside it, tagged by trained annotators and checked. See data annotation.
Reviews and messages labeled positive, negative or neutral by people who catch sarcasm and local slang.
The text carried into other languages with its labels intact, reviewed by people who know the language. See translation and localization.
Text written by people in your domain, labels for classes, entities and sentiment, and translation into the languages your users read, Indian languages included.
Prompts, questions, answers and everyday messages, written by people in the languages and the domain you need.
For chat assistants, search and language models
Each message gets one label from a set you agree on, with a clear rule for what counts as "other".
For routing, intent detection and content filters
Names, products, places, dates and times marked in the text, so your model can pull them out on its own.
For assistants, search and document reading
Reviews, chats and messages labeled positive, negative or neutral, sarcasm included.
For feedback analysis and brand tracking
Text translated into the languages your model has to handle, with a linguistic and cultural review on top of any machine draft.
For multilingual assistants and datasets
Our tool: Translation Free sample of text translation
Text in Indian languages well past Hindi, in native scripts and in the Latin letters people often type on phones.
For apps and assistants built for India
Common uses for text data. They're examples of the work, not a list of clients. If your project goes beyond text, see speech data, image data and video data. Two example categories: English e-commerce support text and paired chat and voice support data.
The same request written many ways, so an assistant understands users who don't phrase things like the docs.
Messages labeled by topic and urgency, so a model sends each one to the right place.
Products, dates and places tagged, so a model can pull out what the user actually asked for.
Reviews labeled for sentiment, sarcasm included, so a model reads the mood correctly.
Text in every language your product supports, native scripts and Latin letters included.
Held-back text in each language and domain, to check your model where it matters.
Each page covers what that kind of text project usually needs, and each one is built to your brief. Every category, including speech, image and video, is on the datasets hub.
Get these wrong and no amount of volume fixes it. We settle them with you at the start.
Written new by people from our network, or your own text to label, or both.
Every class and entity type, including what counts as "other", agreed before the first label.
Which languages, and whether text is written in native scripts, Latin letters or both.
Whether writers use invented names and details, and what the text may be used for afterward.
One named person looks after the project. Each step links to the service that handles it.
You tell us the domain, the languages and what the text is for.
The NDA is signed before any data moves.
People from our network write the text in their own words.
Annotators label it, and every batch is reviewed.
Text carried into other languages, labels intact.
Held-back text checks your model language by language.
We work in languages from all over the world and go deep on Indian ones, well past Hindi and English, in native scripts and in Latin letters. Our page on Indian language data has the details.
Short definitions for the words that come up on language projects.
Text work usually spans a few of these. You can also compare all eight.
Text written by people in our network.
Classes, entities and sentiment labeled.
Text carried into other languages.
Dialogue for chat and voice assistants.
Generated text for rare cases, reviewed by people.
Common questions about text data. The services FAQ covers how the services fit together.
Written language paired with labels, like the intent behind a message or the names and dates in it, that a language model learns to read or write from.
People from our 30,000+ network, in the languages and the domain you need: prompts, questions, answers and everyday messages.
Yes. Trained annotators label your text for classes, entities and sentiment, and every batch gets a multi-level review. See data annotation.
Languages from all over the world, with deep coverage of Indian languages, including text in native scripts and in Latin letters. Our Indian language data page has more.
Yes. Translation runs in our own Translation tool, with a linguistic and cultural review on top. See translation and localization.
It depends on the task, the number of labels and how varied your users are, so there's no standard number. We plan it with you, and the free sample shows quality before you commit to volume.
Yes. Send a short brief and we'll write or label a small sample free before you commit.
Yes. The NDA is signed before any data moves, we use it only for the scope we agreed, and only the people working on your project can get to it. It's returned or deleted when you ask.
Pick what you need, add the languages and roughly how much text, and send it. We'll write or label a small sample free before you commit.
This opens your email app with the brief filled in. Nothing is sent until you press send. You can also use the contact page.