Jev 1.14 from @typesafeai can't do this.
TypeLLM can detect every vehicle in an image and return an array of bounding boxes — including @Tesla's new flying Roadster.
Try it now: typellm.ai/cookbook/locate-v…
Cloudflare just previewed Clairic, a system-one extraction model.
We ran it on a simple table extraction example:
TypeLLM: 20/20 rows correct
Clairic: 1/20 rows correct
Try it yourself 👇 colab.research.google.com/gi…
a brand new model paradigm! introducing 𝚌𝚕𝚊𝚒𝚛𝚒𝚌: a system one model for extracting, computing, estimating, and predicting values from unstructured inputs.
blog.cloudflare.com/clairic-…
TypeLLM retweeted
This team is totally switched on right now.
Workers AI is in their lore building era. Glad I get to be close to it.
a brand new model paradigm! introducing 𝚌𝚕𝚊𝚒𝚛𝚒𝚌: a system one model for extracting, computing, estimating, and predicting values from unstructured inputs.
blog.cloudflare.com/clairic-…
We need a different way to interact with powerful models.
Instead of the chat API, you submit a workflow. The model executes it and returns the results.
The "support" of intelligence is controlled without compromising prediction accuracy.
This is the vision behind TypeLLM.
Closed frontier LLMs are dangerous
In most post-training reasoning efforts, a pre-trained base model trains on its own chains of thought (CoTs) when a final-answer verifier says the answer is correct. This is the basic principle of RL methods based on outcome rewards, used for STEM reasoning, coding tasks and even ethical alignment. Different algorithms have weigh the CoTs differently, but they all reinforce CoTs.
As we've shown, training on one's own data, while not knowing how to distinguish it from someone else's data, causes delusions. See love4all.ai/files/why-it-is-…
Everyone knows the different between something they did and something someone else did. This is essential for safety. If I write "Kevin is unfriendly" on a napkin, go for a walk, and then read the message on the napkin not knowing who wrote it, then my belief that "Kevin is unfriendly" is reinforced.
These delusions are essentially confabulations, over-confidence that results from confusing P(o | a) with P(o | do(a)), where o is an outcome and a the action (CoT tokens). Unlike in past work, here I'm alerting everyone to this danger when training models to think, a typical step in the process of building agents.
When the verifier supplies one bit about the answer, algorithms like ReST or GRPO spread that bit over every token of the CoT trace, so a reasoning step that is wrong but happens to precede a correct answer (a false lemma, a shortcut that only works on the training distribution, a sycophantic or test-gaming rationale, a subtle bias) is reinforced.
Traits that are merely neutral are sharpened by mode-seeking self-distillation, and traits that are spuriously correlated with success grow exponentially.
The damage may be invisible to the researchers and metrics, and in-distribution accuracy rises, but it shows up off-distribution.
There has been some work on this. For example, Appendix G of the STaR paper arxiv.org/pdf/2203.14465 touches on this potential bias amplification but only on the surface. Some researchers have proposed process rewards as the solution arxiv.org/pdf/2211.14275
However, self-delusion by mistaking ones actions with observations produced by a third party highlights that this problem can be much more serious.
Something subtle, invisible to the metrics and to the researchers, could lurk in the synthetic data. When deploying the AI out of distribution, that something could be fatal.
Don't trust RL, RLHF, etc, blindly unless you really understand how the verification has been done. Corollary, don't trust any of the closed frontier models.
New in the TypeLLM API today: Array generation is now more complete and faster — with up to 34% higher recall and 27% lower latency.
Try it for object detection or document parsing:
typellm.ai/cookbook/dense-pa…
A clarification: Jev only supports one bounding box per question.
This means that if an image contains multiple objects of the same category, Jev cannot return all their bounding boxes in a single call, since the questions are independent.
You can test this by uploading an image containing several dogs and asking Jev to return all their bounding boxes.
docs.typesafe.ai/primitives/…
Jev 1.14 is a big improvement, but it still has a limit of 255 classes.
What if you need to classify across more than 255 classes, such as time zones?
TypeLLM supports up to 512 classes natively.
Try it now: typellm.ai/cookbook/classifi…
Chat models return messages.
Decision models return decisions.
Workflow models execute workflows.
TypeLLM introduces the first workflow model. Run an entire workflow in a single API call.
Simpler, faster, cheaper.
Try it now: typellm.ai/examples/ticket-w…
RCA is a great usecase of TypeLLM
Lots of non-tech posts from me lately, so here's proof I still write code.
I swapped the decision model inside my root-cause agent from @typesafeai Jev to @TypeLLM. Same code, 60 incidents.
Same accuracy. TypeLLM proved its answer 10x more often, for 36% less. Jev was faster.
TypeLLM allows you to define your whole workflow in one JSON API call.
Now you can visualise your workflow in the playground
Try it now: typellm.ai/dashboard/playgro…
A new model is coming to the TypeLLM API!
OpenAI Decisions, Jev, Microsoft Decision-1, Cloudflare Clef — all capped at 255 options.
TypeLLM is pushing the limit to 512 options, with probabilities and confidence scores for every choice
Try it now: typellm.ai/cookbook/classifi…
Jev is great at classification.
But what if the classes aren't known in advance?
We show how to use TypeLLM to discover new categories on the fly.
typellm.ai/cookbook/discover…
TypeLLM API vs OpenAI Decisions API: bet on the suit of a random card
After 100 rounds, TypeLLM holds over 90% of the pool.
Try it: colab.research.google.com/gi…









