How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LINDAT NameTag API

Public keyless REST API for named-entity recognition and tokenization (NameTag 3) operated by UFAL at Charles University via LINDAT/CLARIAH-CZ. The OpenAPI here is derived by API Evangelist from the service's own published REST API reference and verified against live responses.

LINDAT NameTag API is one of 17 APIs that Charles University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Natural Language Processing, Named Entity Recognition, and Research. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 3.

Requests are made against a single base URL, https://lindat.mff.cuni.cz/services/nametag/api.

5 operations 3 paths 4 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3
Base URL
https://lindat.mff.cuni.cz/services/nametag/api
Terms of Service
Resource Areas
1

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

nametag 5

Named-entity recognition and tokenization operations

GET
/models
List available NameTag models
listNameTagModels → 200
GET
/recognize
Recognize named entities in supplied text
recognizeEntities 4 params → 200
POST
/recognize
Recognize named entities in supplied text (form-encoded or file upload)
recognizeEntitiesPost body → 200
GET
/tokenize
Tokenize supplied text
tokenizeText 3 params → 200
POST
/tokenize
Tokenize supplied text (form-encoded or file upload)
tokenizeTextPost body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are RecognizeRequest (4 properties), TokenizeRequest (3 properties), ServiceResponse (3 properties), ModelList (2 properties). Each schema is shown below with its type and property counts.

ModelList
object
Inventory of available models and the methods each supports.
2 properties 2 required
ServiceResponse
object
Common LINDAT web-service response envelope.
3 properties 2 required
RecognizeRequest
object
4 properties 1 required
TokenizeRequest
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

charles-nametag-api-openapi.yml Raw ↑

Other APIs Charles University publishes across the network.

LINDAT Translation Languages API
LINDAT Translation Models API
LINDAT Translation Root API
LINDAT UDPipe API
LINDAT MorphoDiTa API
LINDAT Korektor API
CU Digital Repository OAI-PMH
CU Research Publications Repository OAI-PMH
LINDAT/CLARIAH-CZ Repository OAI-PMH
LINDAT/CLARIAH-CZ Repository REST API
Charles University Shibboleth Identity Provider
DataCite Registrant — Charles University (CUNI)
Where this information came from

This is an independent, third-party profile of LINDAT NameTag API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.