Estonian National Corpus 2017

Open data API in a single place

Provided by Eesti Keele Instituut

Get early access to Estonian National Corpus 2017 API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Eesti Keele Instituut catalog

Country of origin

Estonia

Updated

2024.05.16 00:00

Created

2023.06.08

Available languages

English

Keywords

[object Object]

Datasource

Official portal for European data link

Quality scoring

Dataset description

The corps was established in cooperation between the Estonian Language Institute and Lexical Computing Ltd. The size of the corps is 1.3 billion words. The base of the corps is the Estonian Language Joint Corps 2013, which was renewed by Lexical Computing Ltd. in 2017 on the order of the Estonian Language Institute. The sub-corps are the Estonian language corps 1990-2008, the Estonian language web corps 2013, the Estonian language web corps 2017 and the Estonian Wikipedia 2017 corps. The content of the web housing is Estonian-language websites downloaded from the Internet. The programs described at http://corpus.tools have been used to create the housing: SpederLing, JustText, Chared, Onion and wiki2corpus. The housing is lemmatized, marked and connected by the EstNLTK analyser.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service