Bethmardutho SEDRA IV API

Name: SEDRA IV API
Brand: SEDRA IV API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationLmsnone2 EndpointsREST

For Agents

Look up Syriac words and lexemes by SEDRA id or vocalised text in the SEDRA IV linguistic database.

Install Jentic One Beta

Connect the SEDRA IV API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SEDRA IV API, 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 SEDRA IV API.

Look up a Syriac word by SEDRA word id

Look up a Syriac word by fully, partially, or non-vocalised Syriac text

Retrieve a lexeme entry with grammatical metadata by lexeme id

Cross-reference word forms to their lexeme parents

GET STARTED

Start building with SEDRA IV API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for SEDRA IV API, keeping it validated and agent-ready. The SEDRA IV API exposes the Syriac Electronic Data Research Archive — a linguistic and literary database of Syriac lexicons with grammatical and morphological information for each entry. It supports word lookup by SEDRA word id or by Syriac text in consonantal, partially vocalised, or fully vocalised forms, and lexeme lookup by id. The spec is small but specialised, with two read-only endpoints serving JSON for academic and digital humanities applications.

Use Cases

Patterns agents use SEDRA IV API for, with concrete tasks.

★ Syriac Reading Tool

Build a Syriac reading or learning tool that resolves clicked words to their full SEDRA entries, returning grammatical information, root, and lexeme. The /word/{id} endpoint accepts both SEDRA numeric ids and Syriac text in any vocalisation, while /lexeme/{id} returns the underlying lexeme. CORS is enabled, so a static page can call the API directly without a backend.

Given the clicked Syriac word ܐܰܒܳܪܳܐ, GET /word/ܐܰܒܳܪܳܐ.json and render the lexeme reference plus grammatical fields

Lexicon Cross-Reference

Cross-reference a corpus of Syriac texts against the SEDRA lexicons to produce a frequency or concordance list. Each unique word form can be resolved through /word/{id} and grouped by the lexeme returned through /lexeme/{id}. Building a corpus enrichment pipeline is typically half a day to a day depending on input size and caching strategy.

For each word form in a Syriac text, GET /word/{form}.json and aggregate the lexeme ids to produce a frequency list

Digital Humanities Research

Use SEDRA as a structured data source for digital humanities research on Syriac language and literature. The two endpoints expose deterministic JSON for word and lexeme lookups, suitable for scripted batch enrichment of historical manuscripts or critical editions. Combined with a manuscript transcription pipeline, SEDRA can resolve every word to its lexeme entry overnight.

Iterate every transcribed word in a manuscript JSON file and call /word/{form}.json to attach SEDRA grammatical metadata

AI Agent for Linguistic Lookups

An AI agent uses Jentic to discover SEDRA's word and lexeme operations and answer Syriac language questions in chat. The agent searches by intent, loads the operation schema from Jentic, and executes the lookup against SEDRA without parsing the bespoke ReDoc page. Because SEDRA is unauthenticated, integration via Jentic is essentially zero-config.

Search Jentic for 'look up syriac word' and execute the returned /word/{id} operation with the user's input form

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for sedra iv api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/word/{id}

Look up a Syriac word by SEDRA id or Syriac text

GET

/lexeme/{id}

Look up a lexeme by id

GET

/word/{id}

Look up a Syriac word by SEDRA id or Syriac text

GET

/lexeme/{id}

Look up a lexeme by id

Why Jentic?

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

Credential isolation

SEDRA IV is a public unauthenticated API, so there are no secrets to store. Jentic still routes the call through its execution layer for consistent observability and rate-limit awareness alongside other agent tools.

Intent-based discovery

Agents search Jentic by intent such as 'look up syriac word' and Jentic returns the /word/{id} operation with its parameter schema, including the accepted forms (SEDRA id, vocalised, or consonantal text).

Time to first call

Direct SEDRA integration: a few hours to read the ReDoc page and handle URL-encoded Syriac characters. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using SEDRA IV API through Jentic.

Why is there no official OpenAPI spec for SEDRA IV API?

Beth Mardutho does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call SEDRA IV API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the SEDRA IV API use?

The SEDRA IV API requires no authentication — it is a public read-only endpoint with CORS enabled, and responses are wildcard same-origin. There are no credentials to store in the Jentic vault for this API; agents call it directly through Jentic with no key configuration.

Can I look up a Syriac word by its consonantal form?

Yes. GET /word/{id} accepts a SEDRA word id, a fully vocalised form, a partially vocalised form, or a consonantal form. Accuracy is highest for SEDRA ids, followed by fully vocalised, partially vocalised, and consonantal forms in that order.

How do I retrieve a SEDRA word entry through Jentic?

Run pip install jentic and search for 'look up syriac word'. Jentic returns the GET /word/{id} operation, the agent loads the schema, and executes with either the numeric id (for example 30862) or the Syriac text. The response is JSON with grammatical and lexeme references.

What rate limits apply to the SEDRA IV API?

The OpenAPI specification does not document explicit rate limits. SEDRA is a research service, so be considerate with bulk lookups — cache responses locally and avoid hammering the live host with overlapping concurrent requests.

Is the SEDRA IV API free to use?

Yes. SEDRA is provided by the Beth Mardutho project as an open research resource, with no API key or commercial tier. CORS is enabled so it can be called from the browser, and the same endpoints are available to scripted clients via Jentic.