<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Peter Abolins</title>
    <description>The latest articles on DEV Community by Peter Abolins (@peterabolins).</description>
    <link>https://dev.to/peterabolins</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3885970%2F5f3eb978-3030-436c-96b0-a7da7fe1cda7.jpg</url>
      <title>DEV Community: Peter Abolins</title>
      <link>https://dev.to/peterabolins</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/peterabolins"/>
    <language>en</language>
    <item>
      <title>Building the Romanian NLP API that should already exist</title>
      <dc:creator>Peter Abolins</dc:creator>
      <pubDate>Sat, 18 Apr 2026 11:47:45 +0000</pubDate>
      <link>https://dev.to/peterabolins/building-the-romanian-nlp-api-that-should-already-exist-2gg7</link>
      <guid>https://dev.to/peterabolins/building-the-romanian-nlp-api-that-should-already-exist-2gg7</guid>
      <description>&lt;p&gt;If you've tried to do anything programmatic with Romanian text, you've probably hit the same wall I did.&lt;/p&gt;

&lt;p&gt;There's no clean API for it. You end up scraping DEXonline, wrestling with incomplete library support, or calling a general-purpose LLM and hoping it gets the grammar right. None of that is good enough for production.&lt;/p&gt;

&lt;h3&gt;
  
  
  The specific gap
&lt;/h3&gt;

&lt;p&gt;Given an arbitrary Romanian sentence, return for each token: its lemma, part of speech, grammatical case, number, gender, person, and tense.&lt;/p&gt;

&lt;p&gt;This is what spaCy does for English, French, and German in a &lt;code&gt;pip install&lt;/code&gt;. For Romanian, no equivalent exists as a callable REST API.&lt;/p&gt;

&lt;p&gt;Romanian NLP tooling sits at roughly &lt;strong&gt;15% of what exists for English&lt;/strong&gt;. The academic resources are there — DEXonline (313k+ lemmas), RoLEX (330k morphosyntactic entries), the Universal Dependencies Romanian Treebank — they're just not packaged in a way developers can actually use.&lt;/p&gt;

&lt;h3&gt;
  
  
  But why not just use ChatGPT?
&lt;/h3&gt;

&lt;p&gt;Fair question. The short answer: for production, an LLM is not infrastructure — it's an oracle. The accusative form of &lt;em&gt;câine&lt;/em&gt; is always &lt;em&gt;câinele&lt;/em&gt;, regardless of the LLM's mood that day. LexicRo returns deterministic, structured linguistic data by contract. Beyond that: LLM costs at scale are unpredictable; a dedicated conjugation endpoint responds in under 50ms vs 500ms–3s for an LLM call; and structured output from an LLM requires prompt engineering, validation, and retry logic. LexicRo returns clean JSON, every time.&lt;/p&gt;

&lt;h3&gt;
  
  
  What I'm building
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;LexicRo&lt;/strong&gt; — an open-core, hosted API platform covering the endpoints Romanian developers actually need:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;POST /analyze
→ lemma, POS, case, gender, number, person, tense per token

GET /conjugate/{verb}
→ full conjugation table — all moods and tenses including
  perfect simplu and viitor I (both tested at B1+)

GET /inflect/{word}
→ all inflected forms across cases, numbers, genders

GET /lookup/{word}
→ lexical data from DEXonline: definition, gender, plural, etymology

POST /difficulty
→ CEFR level scoring (A1–C2), calibrated to Romanian B1/B2 exams
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Technical approach
&lt;/h3&gt;

&lt;p&gt;Not starting from scratch — the data and models are there:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Base model&lt;/strong&gt;: &lt;code&gt;bert-base-romanian-cased-v1&lt;/code&gt; fine-tuned for morphological tagging&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Conjugation&lt;/strong&gt;: verbecc Romanian XML templates, extended with full B1+ tense coverage&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lexical&lt;/strong&gt;: DEXonline database dump + RoLEX dataset&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Infrastructure&lt;/strong&gt;: FastAPI, Docker, full OpenAPI spec, Python and JS SDKs&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Licence and access
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Code: MIT (self-hostable)&lt;/li&gt;
&lt;li&gt;Model weights: CC BY-NC 4.0 (free for research/non-commercial, commercial use via hosted API)&lt;/li&gt;
&lt;li&gt;Free tier: 1,000 req/day, no credit card, all endpoints&lt;/li&gt;
&lt;li&gt;Paid tiers from €9/month for production use&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Phase 1 ships first
&lt;/h3&gt;

&lt;p&gt;The conjugation and lexical lookup endpoints are the straightforward part — wrapping verbecc and DEXonline cleanly. That's what ships first (~3 months). The morphological analyser (the hard part, requiring fine-tuned BERT) follows in phase 2.&lt;/p&gt;

&lt;h3&gt;
  
  
  What I'm looking for
&lt;/h3&gt;

&lt;p&gt;I'm in pre-development and genuinely looking for:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Feedback on the endpoint design&lt;/strong&gt; — does this cover what you'd actually need?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Early users&lt;/strong&gt; working with Romanian text at any scale&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Academic connections&lt;/strong&gt; — pursuing EU grant funding (Horizon Europe, CEF Digital)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anyone who's built adjacent to this&lt;/strong&gt; — what did you learn?&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;&lt;strong&gt;Links&lt;/strong&gt;: &lt;a href="https://lexicro.com" rel="noopener noreferrer"&gt;lexicro.com&lt;/a&gt; · &lt;a href="https://github.com/LexicRo" rel="noopener noreferrer"&gt;github.com/LexicRo&lt;/a&gt; · &lt;a href="mailto:contact@lexicro.com"&gt;contact@lexicro.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Romanian deserves the same NLP infrastructure as French or German. Building it in public — feedback welcome.&lt;/p&gt;

</description>
      <category>nlp</category>
      <category>romanian</category>
      <category>api</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
