Digitallinguistics DLx

✓ Official Vendor SpecEducationLmsapiKey18 EndpointsREST

For Agents

Manage language and lexeme records for linguistic field-work projects through the DLx REST API.

Install Jentic One Beta

Connect the DLx to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DLx, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DLx API.

Catalogue languages with metadata such as ISO codes, family, and location

Store and retrieve lexeme entries linked to a language record

Look up entries by language and lexeme identifier

Update lexeme glosses, transcriptions, and morphological data

GET STARTED

Start building with DLx API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DLx API for, with concrete tasks.

★ Field Linguistics Data Capture

Capture and store lexeme entries collected during language documentation field work. The /languages and /lexemes endpoints let researchers register a language and post lexeme records with transcription, gloss, and morphological metadata, building a structured corpus that other DLx-compatible tools can read. This replaces ad-hoc spreadsheets used by many documentation projects.

Register language with ISO code yuk, then post lexeme records for each entry collected in today's session with transcription and gloss

Cross-Tool Lexicon Sync

Synchronise a lexicon between desktop linguistic tools (FieldWorks, Toolbox) and the DLx web platform. The DLx REST API serves as a neutral hand-off point - desktop tools push entries via /lexemes and the web platform reads them back, so collaborators on different tools share one corpus of record.

Read lexemes for language id en-us-app, transform them to FieldWorks XML, and write them out to the desktop tool's project file

Public Language Resource Browser

Build a public browser over DLx-registered languages and their lexemes for educational and reference use. GET /languages lists languages and GET /languages/{languageID}/lexemes returns lexeme records, enabling a static-site generator to produce per-language pages without a live database.

For each registered language, fetch its lexeme list and generate a static HTML page listing transcriptions and glosses for public access

AI Agent Linguistic Research Assistant

An AI assistant supporting linguistic research can query DLx through Jentic to fetch language metadata or lexeme entries on demand. Searching for "list lexemes for a language" returns the matching DLx operation and its schema, so the agent can answer field-data questions without a custom integration.

When the researcher asks "what lexemes have we recorded for Yurok?", call /languages/{languageID}/lexemes with the Yurok language id and summarise the results

Key Endpoints

18 endpoints — the digital linguistics (dlx) rest api stores and serves linguistic field data - languages, lexemes, texts, and metadata - for researchers documenting and analysing the world's languages.

METHOD

PATH

DESCRIPTION

GET

/languages

List registered languages

GET

/languages/{languageID}

Retrieve a language record

GET

/languages/{languageID}/lexemes

List lexemes for a language

GET

/languages/{languageID}/lexemes/{lexemeID}

Retrieve a specific lexeme entry

GET

/lexemes

List or search lexemes globally

GET

/lexemes/{lexemeID}

Retrieve a lexeme by id

GET

/languages

List registered languages

GET

/languages/{languageID}

Retrieve a language record

GET

/languages/{languageID}/lexemes

List lexemes for a language

GET

/languages/{languageID}/lexemes/{lexemeID}

Retrieve a specific lexeme entry

GET

/lexemes

List or search lexemes globally

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your DLx API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list lexemes for a language' or 'look up a single lexeme', and Jentic returns the matching DLx operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using DLx API through Jentic.

What authentication does the DLx use?

DLx uses an API key passed in the Authorization header. Keys are issued by the DLx project for registered users. Through Jentic the key is held in the encrypted vault and injected at execution time only.

Can I retrieve all lexemes for a single language?

Yes. GET /languages/{languageID}/lexemes returns the lexeme records linked to that language record, paginated when the list is large. Each entry includes transcription, gloss, and morphological fields.

What are the rate limits for the DLx?

DLx is a research project and does not publish a fixed public rate limit. Polite use is expected; bulk imports should be batched and spaced out, and any 429 responses respected with backoff.

How do I list lexemes for a language through Jentic?

Run a Jentic search for "list lexemes for a language". Jentic returns GET /languages/{languageID}/lexemes with its path-parameter schema. Load it, supply the language id, and execute - no need to read the DLx spec.

Does the API support the full set of CRUD operations on lexemes?

The published spec exposes read access on languages and lexemes plus a small number of write paths for registered users. For destructive operations, project policy may require additional authorisation beyond the API key.

How do I install the Jentic SDK to call DLx?

Run pip install jentic, set JENTIC_AGENT_API_KEY to your ak_* key, then use Jentic with SearchRequest, LoadRequest, and ExecutionRequest. Get started with Jentic One, the self-hosted execution layer.

Can I limit what my agent is allowed to do with the DLx API?

Yes. Because you self-host Jentic One, your own rules decide which DLx operations the agent may call and which API key it uses. Since the language id sits in the URL path, such as /languages/{languageID}/lexemes, you can pin the agent to a single language so it only reads that language's records and lexemes. You can also limit it to read paths like GET /languages and GET /lexemes and leave global cross-language listing out unless you add it.