Skip to content
→Connect your ad data to any model
Decision models · Early access

Jev for paid media: where a decision model actually fits (2026)

Jev returns a typed decision with a confidence estimate instead of a paragraph. That sounds like a small difference and it changes the economics of one specific thing: judgment calls you need to make thousands of times.

It also cannot see your ad account or change anything in it. This page covers what Jev does, what it does not, and the architecture for pairing it with Meta and Google Ads data.

The short version

  • →Jev answers typed questions — pick one, score this, is this true — and returns a confidence estimate with every answer.
  • →On its own it has no ad-platform access and cannot change anything. It is infrastructure, not a marketing tool.
  • →GoMarble supplies the two halves it is missing: reading the account and executing the change.
  • →Together they make row-level judgment economic: search terms, creative attributes, feed items, comments — thousands of small calls.

1. What Jev is

Jev is a decision model. Ask a language model something and you get prose back, which your code then has to parse. Ask Jev and you get a typed value — a label, a number or a probability — that code can use directly. Every answer carries a confidence estimate.

TypeSafe AI calls this class a System One model, after fast intuitive thinking rather than the slower deliberate kind.

It entered early access on 15 September 2026. Developers are admitted from a waitlist.

There are three primitives:

PrimitiveWhat it doesReturns
ChoiceChoose an option from a listchoice, probabilities, confidence
ScoreScore the state on a rubricscore, probabilities, confidence
NoulIs this statement true?noul (0–1)

All three can be mixed in a single call, and every question in that call is evaluated in parallel. Input costs $42 per billion tokens and output is not charged. Responses come back in well under a second.

The confidence estimate is the part that matters operationally. A verdict you can threshold is a verdict you can automate — send the confident ones straight through, route the rest to a person.

2. What it cannot do on its own

Jev is narrow by design, and the boundaries are where most of the practical decisions live. Five things it does not do:

It cannot read your ad account

Jev has no Meta or Google connection. It answers questions about data you hand it, which means getting that data out of the platforms is a separate problem you still have to solve.

It cannot change anything

There is no write path to any ad platform. A verdict of “this search term is irrelevant” does nothing at all until something adds the negative keyword.

It does not explain itself

You get a value and a confidence estimate, not reasoning. That is the design rather than a shortcoming — but it means Jev cannot tell you why CPA rose. It can only answer questions you already knew to ask.

It needs a fixed question and a fixed answer space

Every primitive requires the question and the possible answers defined up front. If you cannot write the label list, the work is still exploratory and belongs to a person first.

It does not pay off at small volume

Two hundred search terms do not justify a pipeline. Below a few hundred rows, someone with a spreadsheet is faster and you should not build anything.

Put together, those five add up to one thing: Jev is the middle of a workflow. It is not the workflow.

3. Where GoMarble comes into the picture

Jev is missing exactly two things: a way to read the account and a way to act on the answer. Those are the two things GoMarble already does.

StageWhat happensWho does it
1. ReadPull the rows — search terms, ads, feed items, commentsGoMarble MCP
2. JudgeOne typed question per row, with a confidence estimateJev
3. ActExecute the confident verdicts; queue the rest for a humanGoMarble AI Agents

GoMarble already does stages one and three. Its MCP servers read Meta, Google, TikTok, LinkedIn, Bing, Shopify, GA4 and Klaviyo. Its Agents make the changes — bids, budgets, pausing, scaling — once you approve them. Jev fills the gap in the middle.

Why keep the stages separate? Because each one costs you something different. Reading is slow, because ad platforms limit how fast you can pull data. Judging costs money per row. Acting needs permission to touch the account. Hand all three to a single language model and you pay premium prices for work a classifier does better and faster.

There is a second reason this pairing works. Our MCP servers are open, so any tool that speaks MCP can connect to them. That means you choose what sits in the middle — and you are not waiting for anyone to build an integration first.

To be clear about what exists today: this is an architecture you can build, not a shipped feature. GoMarble does not currently bundle Jev.

4. Things you can do with Jev + GoMarble

The test for whether a job fits is simple. Is the judgment small, identical in shape every time, and repeated thousands of times? These five qualify.

What you doPrimitiveThe question per rowTypical volume
Triage search terms on GoogleNoul“This term matches what we sell”1k–50k / month
Classify ad copy angle on MetaChoiceWhich angle does this headline use?100–5k ads
Score line items for wasteScoreHow likely is this pure waste?1k–20k rows
Classify a shopping feedChoiceWhich category does this product belong in?1k–100k SKUs
Triage ad commentsChoiceComplaint, question, spam or praise?100–10k / week

Notice what is not on that list: anything needing a narrative. “Why did ROAS fall” is one question with a complicated answer — the opposite shape, and a job for a reasoning model or for GoMarble’s own root-cause analysis.

Notice what is missing from that list

Every row above operates on text. None of them looks at the ad itself — and that is the limit that matters most for marketers.

5. Why Jev is not yet the most useful tool for marketers

Jev is text-only. The state you send it can be a string, a JSON object or an array of text values, and that is all — no image, audio or video input. For paid media that rules out most of the interesting work, because the interesting work is visual. Here is what that costs you in practice:

It cannot see the ad

  • Which hook a video opens on
  • Whether a thumbnail is cluttered or a static ad buries its offer
  • How two creative variants actually differ
  • Whether an image breaks brand guidelines

All of that needs a model that can see the asset. Any demo where Jev appears to read a screenshot is doing the perception somewhere else first.

It decides, it does not describe

  • Explaining why CPA moved — that is a narrative, not a label
  • Drafting a client email or a weekly performance summary
  • Writing a creative brief from what worked

Anything a person reads is prose, and prose is what a language model is for.

It needs the question settled in advance

  • Weaker whenever the label set is incomplete — exactly the case when you are exploring a new account and do not yet know the categories
  • Arithmetic, counting and date maths are not what it was optimised for, so pacing and period-over-period calculation belong in code
  • Non-English text is handled but not equally well across scripts, which matters for international accounts

None of this makes Jev a bad model. It makes it a narrow one, and the narrowness is the design rather than a gap waiting to be filled. The honest read for a marketing team in September 2026: Jev is useful for one shape of problem — high-volume, text-based, fixed-label judgment such as search-term triage — and almost everything else on your list is still better served by a language model, a vision model, or plain code. If your bottleneck is creative, Jev does not touch it yet.

FAQ

What is Jev?
Jev is a decision model — a System One model, in TypeSafe AI’s terminology — that returns typed decisions with probabilities and a confidence estimate instead of free-form text. It has three primitives: Choice, Score and Noul.
Can Jev analyze my Meta or Google Ads account?
Not on its own. Jev has no connection to ad platforms and no ability to change anything in an account. It answers typed questions about data you send it, so it needs a data layer to read the account and an execution layer to act on the verdict.
How is Jev different from using an LLM for the same task?
An LLM returns prose you then have to parse, and its price and latency make per-row calls expensive at volume. Jev returns a typed value with a confidence estimate, which is what makes classifying thousands of rows practical rather than a batch job you keep postponing.
What does Jev cost?
Input is $42 per billion tokens and output is not charged. It is in early access, so verify current pricing before budgeting against it.
Is Jev generally available?
No. As of September 2026 Jev is in early access with developers admitted from a waitlist, and its request format is not fully published. Treat any integration as provisional.
Does GoMarble integrate with Jev?
Not today. GoMarble’s hosted MCP servers expose ad-account data and actions to any client that speaks MCP, which is what makes the architecture on this page something you can build yourself rather than wait for.
Which paid-media task fits Jev best?
Search-term triage on Google. The judgment is binary, the volume is high, and search terms are exposed by the platform — so the data is available and the verdict maps directly onto a negative keyword.
When should you not use Jev?
When you need an explanation rather than a verdict, when the output is prose for a person to read, or when the volume is a few hundred rows. Diagnosing why ROAS moved needs reasoning, not classification.

Sources & methodology

Jev’s primitives, pricing, input modalities and availability were reviewed on 25 September 2026 against TypeSafe’s site and documentation, linked below. The text-only constraint and the stated weaknesses come from TypeSafe’s own model documentation for jev-1.13.0. Jev is in early access and both pricing and API surface may change. The architecture described here is a pattern you can build, not a shipped integration — GoMarble does not currently bundle Jev.

Your ad data, open to whatever model you choose.

GoMarble's hosted MCP reads Meta, Google, TikTok and Shopify, and Agents execute the changes. Connect in one click and see the read-and-act half working on your own account.