Tag

Structured output

4 articles tagged with “Structured output”

The Paralon capybara plugging a glowing cable into the last block of a workflow diagram
Guides & Tutorials

11 min read

Using n8n with an Open LLM API: One Credential Field, One Toggle, and the Node That Will Not Work

n8n talks to any OpenAI-compatible endpoint through the Base URL field of its OpenAI credential, and its OpenAI Chat Model node lists whatever /v1/models returns. n8n's OpenAI nodes now default to the Responses API, which most open endpoints answer with a 404; ours serves it, and both the Chat Model and the OpenAI node's Message a Model work. The setup, tested on n8n 2.38, a ticket-triage workflow you can import, and the one Extra Body line that cut the model's answer from 3.3 s to 1.0 s.

Read
The Paralon capybara seated as a judge with a glowing gavel, weighing two floating sheets on a holographic balance
Guides & Tutorials

13 min read

LLM-as-a-Judge with an Open Model: 990 Planted Errors, 99.6% Caught, and What the Rubric Changes

We used Qwen 3.8 27B over an OpenAI-compatible API as a judge of dataset labels, and scored it against errors we planted ourselves so every number is exact. With a written rubric the judge caught 491 of 493 wrong labels and also rejected 58 labels the dataset called correct, 43 of them the same systematic mistake in the generator. Without the rubric it agreed with the dataset more and missed 20 planted errors. The rubric is not a tuning knob; it decides what the judge measures.

Read
The Paralon capybara sorting a stream of glowing paper sheets into a row of green trays
Guides & Tutorials

13 min read

Document Classification with an Open LLM API: 7,218 Documents, No Training Data, $0.05 per Thousand

We classified the full 20 Newsgroups test split with Qwen 3.8 27B over an OpenAI-compatible API, zero-shot, ten documents per request, with the label set enforced by a JSON schema. 72% accuracy on twenty classes with no labeled data, 70,000 documents an hour on one key, and a third of all errors inside three categories that overlap by definition. Few-shot examples doubled the cost and moved accuracy half a point.

Read
The Paralon capybara holding a magnifying glass over a floating invoice while glowing rows of extracted fields lift off the page
Guides & Tutorials

10 min read

Invoice Data Extraction with a Vision LLM API: 60 Invoices, Every Field Scored, $0.78 per Thousand

We ran 60 invoices, half of them degraded like phone scans, through Qwen 3.8 27B's vision input over an OpenAI-compatible API with a JSON schema on the output. Vendor, customer, invoice number, currency, every amount and every line item came back right on all 60. The one thing that failed, half the time, was a date written with slashes, and the fix is two lines of code, not a bigger model.

Read