Jev PDF text layer check

Check extracted PDF text before choosing an OCR path

Provide extracted page text and parser observations. Distinguish usable content from an OCR candidate or missing evidence; empty text alone does not establish that a page is scanned.

PDF text layer checkLive API
Try an example

Substantive text and coverage are supplied.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Judge the supplied page extraction.

Decision rules and labels
Usable textOCR candidateReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

This is a text-based routing exercise. Paste extracted text and parser facts; the page does not inspect a PDF image.

OCR candidate is a reason to consider an OCR attempt, not a promise that OCR will recover the content. A real pipeline must preserve page order and validate the result.

The linked document router separates readable pages from pages needing OCR. Its third-party measurements are not results for these synthetic samples.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for pdf text extraction review.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide extracted page text and parser observations.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Usable text, OCR candidate, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Readable pageUsable text100%
Image-only contentOCR candidate93.0%
Watermark onlyOCR candidate99.0%
Unknown empty extractionReview99.0%
Broken character mappingOCR candidate99.0%
Conflicting coverageReview94.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

PDF text extraction review: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Testing page-level extraction routing before an OCR integration.
  • Distinguishing watermark text from recovered document content.
  • Flagging extraction records whose parser coverage is incomplete or contradictory.

Outside this demonstration

  • Declaring an empty extraction to be a blank page.
  • Checking layout fidelity or extracting text from an uploaded image here.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Can a page with some text still need OCR?

Yes. Its body may be a scanned image while only a watermark or header is extractable. The supplied parser facts must describe that gap.

Does this upload or process a PDF?

No. The editable example accepts text and parser observations. A separate parser would inspect the file and an OCR service would process selected pages.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.