Provide a reading goal and saved-item summary. Compare useful material for your API-retry work with background reading, unrelated topics and summaries needing review.
Choose a bookmark for this reading goalLive API
The decision
Relevant to what you need to do next.
This example uses a specific objective: implement safe API retries in a Node.js service this week. A summary that teaches bounded backoff or idempotency fits that task immediately. A general discussion of reliability can still be useful, but it goes into Save for later under this rule. A cake recipe is outside the objective, regardless of its quality.
The labels describe the relationship between a supplied summary and a supplied goal. They do not predict a person's click probability or say whether an article is universally good. Elastic's ranking documentation treats relevance as a search problem, and its evaluation guide recommends representative queries and judgments. Here, six synthetic examples expose the rule rather than estimate performance on a real library.
The source post describes classifying saved bookmarks with Jev. We built a smaller independent exercise with editable summaries, explicit choices and recorded API outputs. The source speed and model-comparison claims are not measurements of this page. The tool reads the text you enter; it does not visit saved URLs or infer the contents of a missing article.
AI-generated concept illustration of goal-based reading selection; not a real bookmark manager.
How it works
Build a focused reading shortlist.
Keep the goal, summary and result together.
01
State the current goal
Describe a concrete task and what would make a saved item immediately useful.
02
Supply honest summaries
Use the title and available summary. Mark absent descriptions as missing instead of guessing the linked content.
03
Inspect the choices
Compare direct implementation help, related background, unrelated material and insufficient evidence.
04
Review the reading list
Keep record IDs and the objective. Reclassify when the goal changes and inspect uncertain items before dropping them.
Our API test
Six saved summaries, one explicit reading goal.
Six saved summaries, one explicit reading goal.
Synthetic bookmark
Observed label
Leading probability
Immediate implementation
Read now
100%
Avoid duplicate writes
Read now
96%
Related background
Save for later
97%
Unrelated topic
Not relevant
100%
No useful summary
Needs review
100%
Related but not immediate
Save for later
96%
Six completed live Jev requests on September 27, 2026. Earlier attempts encountered provider failures and are excluded from this result table, not counted as successful tests. No accuracy or speed benchmark is claimed.Verified
Understand the results
Try replacing the technical objective with planning a weekend birthday cake
Try replacing the technical objective with planning a weekend birthday cake.
Read the example notes
Rewrite the four label criteria to match that task, then run the cake summary again. The item has not changed, but its usefulness to the current goal has. That is why the reading objective should be saved alongside each classification.
Source and example scope
Needs review handles the vague title with no summary.
Read the example notes
Fetch or write an authorized summary before treating that item as irrelevant. Save for later is different: the supplied description establishes a related topic, but not enough immediate implementation value for this particular week's task.
Using the result in your application
Download observed-bookmarks.json and run-choice-sample.mjs into a private Node.js project.
Read the example notes
Tested setup is Node.js 24.18.0 and @typesafe-ai/sdk 0.6.0. Run npm init -y and npm install @typesafe-ai/sdk@0.6.0, set TYPESAFE_API_KEY privately, then run node run-choice-sample.mjs observed-bookmarks.json sparse. The runner makes one fresh request without retries.
Using the result in your application
Each fixture sample preserves its ID, full summary, policy, choices and recorded output.
Read the example notes
The runner prints the selected ID, elapsed time and provider result. Fresh distributions can differ. If you later build a ranked feed, evaluate it on your own representative goals and judgments; six illustrative checks do not establish reading-list quality or comparative speed.