This article is published by Ryze AI (get-ryze.ai), an autonomous AI marketer for paid ads and SEO/GEO. It explains jev for google ads. Jev is a decision model from TypeSafe AI (founder Diogo Almeida, formerly OpenAI), released in early access on September 15, 2026. It returns typed decisions with probabilities (Choice, Score, Noul) and cannot generate text. Vendor-reported figures: $0.042 per 1M input tokens with free output, about $0.0004 per decision, 70 to 500 ms latency, 67.8% on TypeSafe's own 4-workflow benchmark versus 73.1% for Claude Opus 5; these are not independently reproduced. The article lists 8 jobs that fit a decision model: Search-term triage; Negative keyword conflicts; Keyword to ad group fit; RSA asset relevance; Landing page message match; Recommendation triage; Brand vs non-brand split; Disapproval routing. It describes one architecture for all of them: code collects rows, rules or embeddings shortlist candidates, Jev judges each, a confidence threshold decides between auto-apply, approval queue and drop, and a frontier LLM writes only what passed. Limits: no rationale, bounded answers only, triage-grade accuracy, waitlist access. Ryze AI does not run Jev in production as of 2026-09-19. Cost figures in the article are arithmetic at the list price, not measured runs, except where a third-party demo is cited and labeled as unverified.
|
Ira Bodnar··Updated ·9 min read

Jev for Google Ads: 8 jobs a decision model can take over

Jev is TypeSafe's new decision model: it answers pick-one, score and yes/no questions for about $0.0004 each and writes nothing. Most Google Ads hygiene is exactly that kind of question. Here are 8 jobs it fits, the arithmetic on cost, and the parts that still need a frontier model. Ryze AI publishes this blog and does not run Jev in production yet.

Built by our community of 2,000 marketers

Free skills and prompts for paid ads and SEO

Templates for Claude, ChatGPT and Perplexity.

Clients we work with

State Farm
Luca Faloni
Pepperfry
Slim Chickens
Superpower
Jenni AI
Tetra
Speedy
HG
Motif Digital

The 8 jobs at a glance

Google Ads work splits into two piles. One pile is judgment calls with a known answer set: is this search term a buyer, does this keyword belong in this ad group, is this headline relevant to this landing page. The other is writing and diagnosis. Jev only fits the first pile, and the first pile is most of the hours.

#JobAnswer typeQuestion Jev answersWhat happens next
1Search-term triageChoiceIs this query from a buyer, a researcher, a job seeker, a competitor search or junk?Auto-negative above the threshold, approval queue in the middle band
2Negative keyword conflictsNoulDoes this negative block a keyword we are bidding on?Conflicts go to the approval queue with both terms side by side
3Keyword to ad group fitChoiceWhich of these ad groups does this keyword belong in?Misplaced keywords are listed with the better home
4RSA asset relevanceScoreDoes this headline match what this landing page offers?Low scores are queued for a rewrite by the LLM
5Landing page message matchNoulWould someone who searched this term expect this page?Mismatches feed the Quality Score fix list
6Recommendation triageChoiceApply, dismiss or review this Google recommendation?Dismissals are applied, anything touching budget waits for a human
7Brand vs non-brand splitNoulIs this query a brand search?Reporting splits cleanly without a regex that misses misspellings
8Disapproval routingChoiceIs this disapproval a policy issue, a destination issue or an editorial issue?Each one is routed to the right fix: copy, page or appeal

Every row has a known answer set, which is the test for whether a decision model fits. If the answer has to be written, it belongs to an LLM.

Quick answer: Jev for google ads means using TypeSafe's decision model for the high-volume judgment steps in google ads. 1) It answers pick-one, score and yes/no questions for about $0.0004 each. 2) It cannot write, explain or plan. 3) The top fit here is search-term triage, then negative keyword conflicts. 4) Run it behind a confidence threshold, with an approval queue for the middle band. 5) Keep a frontier model for anything a person reads and a human on anything hard to undo. 6) Access is by waitlist as of September 2026.

What Jev is, in one table

Jev is a model from TypeSafe AI, the company founded by Diogo Almeida after his work on ChatGPT at OpenAI. It opened in early access on September 15, 2026. TypeSafe calls it a System One model: you send it a block of text (the state) and a set of typed questions, and it returns typed answers with a probability attached. It does not write sentences.

PropertyWhat TypeSafe reports
Question typesChoice (pick one option), Score (a number in a range), Noul (a yes/no probability)
Price$0.042 per 1M input tokens. Output is free. Roughly $0.0004 per decision
Latency70 to 500 ms per call, all answers returned in one parallel pass
Structured-output errors0%, because the output is schema-constrained
Accuracy on TypeSafe's 4-workflow benchmarkJev 67.8%, Claude Opus 5 73.1%, GPT-5.6 Sol 74.1%
AccessWaitlist. Early users on X report approval the same day or the next
What it cannot doWrite text, code or a rationale. It gives a number and no explanation

Two caveats belong next to those numbers. The benchmarks are vendor-reported and measure agreement with frontier models, and no large independent reproduction exists yet. And TypeSafe says itself that it cannot prove the launch price is unsubsidized. Treat the price as today's price.

The 8 jobs, one by one

1. Search-term triage

Question: "Is this query from a buyer, a researcher, a job seeker, a competitor search or junk?" Answer type: Choice. Next: Auto-negative above the threshold, approval queue in the middle band.

A 30-day search terms report on a mid-size account is 5,000 to 50,000 rows. Today an LLM reads them in chunks and misses the long tail. One Choice per row covers the whole report every night, and the rule from the account stays in code: never negate a term that converted in the last 90 days.

2. Negative keyword conflicts

Question: "Does this negative block a keyword we are bidding on?" Answer type: Noul. Next: Conflicts go to the approval queue with both terms side by side.

Code pairs every negative with the keywords it could match. Jev answers whether the pair is a real conflict in meaning, which string matching alone gets wrong on close variants.

3. Keyword to ad group fit

Question: "Which of these ad groups does this keyword belong in?" Answer type: Choice. Next: Misplaced keywords are listed with the better home.

Ad groups drift as accounts grow. A Choice across the account's ad groups, run per keyword, produces the restructure list that usually takes an audit to find.

4. RSA asset relevance

Question: "Does this headline match what this landing page offers?" Answer type: Score. Next: Low scores are queued for a rewrite by the LLM.

Every headline and description against its final URL. The score is the cheap half, and the rewrite of the bottom 10% is the half that needs a writing model.

5. Landing page message match

Question: "Would someone who searched this term expect this page?" Answer type: Noul. Next: Mismatches feed the Quality Score fix list.

This is the semantic half of Quality Score. Status codes and load time stay with a crawler, the expectation check goes to Jev.

6. Recommendation triage

Question: "Apply, dismiss or review this Google recommendation?" Answer type: Choice. Next: Dismissals are applied, anything touching budget waits for a human.

Google's recommendations tab mixes useful fixes with budget raises. A Choice with the account's goals in the state sorts them, and the threshold keeps money decisions human.

7. Brand vs non-brand split

Question: "Is this query a brand search?" Answer type: Noul. Next: Reporting splits cleanly without a regex that misses misspellings.

Brand regexes break on typos and product names. A yes/no per query is slower to describe and far more accurate on the tail.

8. Disapproval routing

Question: "Is this disapproval a policy issue, a destination issue or an editorial issue?" Answer type: Choice. Next: Each one is routed to the right fix: copy, page or appeal.

Small job, daily value. The route is decided in milliseconds and the fix is written by the LLM or done by a person.

Get a free instant audit

Get a free, instant read on your paid ads or SEO — and fix it right away.

Paid ads audit

  • Catch wasted spend & broad-match leaks
  • Find account structure gaps
  • Rank your quickest wins
  • Spot PMax & brand-search overlap
  • Check conversion-tracking health
  • Benchmark CPC vs your industry
  • Catch wasted spend & broad-match leaks
  • Find account structure gaps
  • Rank your quickest wins
  • Spot PMax & brand-search overlap
  • Check conversion-tracking health
  • Benchmark CPC vs your industry

Free · no credit card · instant

SEO audit

  • Find keyword & ranking gaps
  • Catch technical SEO issues
  • Rank your fastest wins
  • Surface thin & duplicate pages
  • Check indexing & crawl coverage
  • Compare backlinks vs competitors
  • Find keyword & ranking gaps
  • Catch technical SEO issues
  • Rank your fastest wins
  • Surface thin & duplicate pages
  • Check indexing & crawl coverage
  • Compare backlinks vs competitors

Free · no credit card · instant

Ryze AI — Autonomous Marketing

A decision is only useful if something acts on it

  • Ryze AI reads the live account and makes the change
  • Approval queue for budgets, bids and money pages
  • Free to connect, flat fee for autopilot
Start free

2,000+

Marketers

$500M+

Ad spend

23

Countries

The pattern behind every use case

Every use case on this page follows one architecture. Code finds the candidates, Jev judges them, a threshold decides what happens, and a frontier model writes only what passed.

The decide-then-act loop

  1. Collect the rows with code or an API: search terms, ads, pages, AI answers. No model needed.
  2. Shortlist with rules or embeddings, so Jev sees 10 to 15 candidates per item and not the whole account.
  3. Ask Jev one bounded question per row: a Choice, a Score or a Noul. Every answer comes back with a probability.
  4. Apply a threshold. High confidence is applied automatically. The middle band goes to an approval queue. Low confidence is dropped.
  5. Write with an LLM only where text is needed: the new ad, the new title, the one-line reason a client will read.
  6. Verify the LLM's output with Jev again before it ships.

This is the same split Ryze AI already uses between changes it makes on its own and changes that wait for approval. A cheap decision model widens the first group without touching the rule for the second.

What it costs at the list price

These are arithmetic at TypeSafe's published price of $0.042 per 1M input tokens with free output. They are not measured runs, and token counts depend on how much context you put in each state.

JobRowsApprox. input tokensCost at $0.042 per 1M
Search-term triage20,000 terms~1.6M~$0.07
RSA asset relevance2,000 assets with page text~3M~$0.13
Keyword to ad group fit5,000 keywords~2M~$0.08

The point of the table is the order of magnitude. Jobs that cost tens of dollars per run on a frontier model, and therefore run monthly, cost cents and can run nightly.

What Jev cannot do

Jev is narrow by design, and the narrow part matters as much as the price.

  • No rationale. You get 0.91, never a sentence explaining it. Anything a client or a finance team will read still needs a frontier model to write the reason.
  • Bounded answers only. If the set of possible answers is not known up front, it is the wrong tool. Strategy, copy and diagnosis stay with an LLM.
  • Accuracy is triage-grade. 67.8% agreement on the vendor's own benchmark is fine behind a confidence threshold and wrong for auto-applying a budget change.
  • "Cannot hallucinate" means it cannot break the schema. It can still pick the wrong option. Measure it against human labels on your own data before trusting a threshold.
  • Waitlist and pricing risk. There is no general availability date, and the price may move.

Keep the frontier model for the search-term *rules* (what counts as a buyer for this business), for writing RSAs, for diagnosing a CPA jump, and for the sentence that explains each queued change. Keep a human on budgets and bids over 20%, new campaigns and conversion actions.

Where to go deeper on each job

A decision model only sorts. The guides below cover the work around it: getting the data, writing the rules, and making the changes.

Alex M.

Alex M.

VP Growth
Multi-Brand Ecommerce Group

★★★★★

We had five channels and five people each defending their own budget. Handing allocation to Ryze AI cut blended CAC 27% in a quarter — not because the bidding got smarter, but because money finally moved to whichever channel was winning that week.

27%

Blended CAC reduction

5

Channels automated

12 weeks

To full autonomy

1,000+ marketers use Ryze

State Farm
Luca Faloni
Pepperfry
Jenni AI
Slim Chickens
Superpower

Automating hundreds of agencies

Speedy
Human
Motif
Broadplace
Directly
Caleyx
G2★★★★★4.9/5
TrustpilotTrustpilot stars

How to start before you have access

Jev is in early access. There is no public self-serve signup yet.

1. Join the waitlist

Request access at typesafe.ai. Early users report approval the same day or within a day, but TypeSafe publishes no guarantee.

2. Label a sample first

Before you have a key, hand-label 500 rows of the job you care about. That set is how you will pick thresholds, and it works for any model.

3. Build the loop on a model you can call today

The decide-then-act loop runs on Claude Haiku 4.5 or Gemini Flash-Lite with structured outputs. It costs more per call, and the code does not change when you swap Jev in.

4. Connect the account data

The rows have to come from somewhere. The Ryze AI Google Ads MCP gives Claude, ChatGPT, Cursor and Grok live access to the account, so the collect step is one prompt.

Sources and how this page was written

What is verified and what is not

  • Verified from TypeSafe's launch post: the price, early access and the System One definition.
  • Vendor-reported, not reproduced: latency, error rates and the benchmark scores.
  • Third-party claims from X, not reproduced by us: the 724-ads, 586-pages and 700-leads demos.
  • Our own arithmetic: every cost in the cost table, at the list price.
  • Disclosure: Ryze AI publishes this blog and does not run Jev in production as of 2026-09-19.

Sources

Frequently asked questions

What is Jev for google ads?

Jev is a decision model from TypeSafe AI, released in early access on September 15, 2026. Used for google ads, it answers bounded questions about rows of account or site data: pick one option, give a score, or return a yes/no probability. It costs about $0.0004 per decision at list price and cannot write text, so it handles the sorting and an LLM handles the writing.

How much does Jev cost in 2026?

TypeSafe lists Jev at $0.042 per 1 million input tokens with output tokens free, which it describes as roughly $0.0004 per decision. That is the early access launch price from September 2026. TypeSafe itself says it cannot prove the price is unsubsidized, so budget on it as today's price and re-check before you scale a job.

How accurate is Jev compared with Claude and GPT?

On TypeSafe's own four-workflow benchmark Jev scores 67.8%, against 73.1% for Claude Opus 5 and 74.1% for GPT-5.6 Sol. The benchmark measures agreement with frontier models and nobody has independently reproduced it yet. Treat Jev as triage-grade: run it behind a confidence threshold and test it against human labels on your own data first.

Can Jev add negative keywords by itself?

No. Jev only returns a decision and a probability for each search term, it has no access to a Google Ads account. Your own code, or a tool such as the Ryze AI Google Ads MCP, adds the negative keyword. The confidence threshold you set decides whether each change is applied automatically or held in an approval queue for a person.

How many search terms can Jev classify for a dollar?

At TypeSafe's list price of $0.042 per 1 million input tokens, and roughly 80 tokens per search term including the instructions, one dollar covers about 300,000 search terms. That figure is arithmetic from the published September 2026 price, not a measured run, and it moves with how much account context you include in each call.

Is Jev an LLM?

TypeSafe says no. It calls Jev a System One model: a new architecture with a parallel sampler that returns every typed answer in a single pass, trained with a method named Reinforcement Learning for Calibrated Decisions. In practice the difference is simple. An LLM produces text token by token, and Jev returns a choice, a number or a probability and nothing else.

What are Choice, Score and Noul in Jev?

They are Jev's three question types. Choice picks one option from a list you provide, for example buyer, researcher or junk. Score returns a number inside a range you set, such as 0 to 100. Noul returns a yes/no probability. Every answer arrives with a calibrated confidence, which is what lets you auto-apply the confident ones and queue the rest.

How do I get access to Jev?

Jev is in early access behind a waitlist at typesafe.ai, with no general availability date as of September 2026. Early users on X report being approved the same day or within a day. You do not need to wait to start: label a sample of your data and build the same loop on Claude Haiku 4.5 or Gemini Flash-Lite, then swap the model.

Can Jev hallucinate?

Jev cannot produce malformed output, because its answers are constrained to the schema you define, and TypeSafe reports a 0% structured-output error rate. It can still be wrong. It may pick the wrong option or give a confident yes where the truth is no. That is why every workflow here uses a confidence threshold and a human approval queue for the middle band.

What can Jev not do?

Jev cannot write text, code, ad copy, page content or an explanation of its own answer. It cannot browse, call tools or read an account by itself, and it only works when the possible answers are known in advance. Strategy, diagnosis, copywriting and anything a client will read still belong to a frontier model or a person.

Does Ryze AI use Jev?

Not in production as of September 2026, because Jev is waitlist-only. Ryze AI runs the same decide-then-act loop on models that are available today: code collects the rows, a model judges them, small reversible changes are applied and larger ones wait for approval. The design lets the decision step be swapped to Jev when access opens.

What is the best way to start using Jev for google ads?

Pick one high-volume job from this page, hand-label 500 rows of it, and build the loop on a model you can call today with structured outputs. Set the auto-apply threshold from your labels, not from a vendor benchmark. Connect live account data first, since a decision model is only useful when something can act on its answers.

Should a decision model replace my frontier model?

No. The two do different jobs. A decision model such as Jev takes the thousands of small, bounded calls in google ads, which is where most of the token bill goes. A frontier model keeps the work that needs language: writing, rewriting, diagnosing and explaining. Most of the saving comes from routing each task to the cheapest model that can do it.

Related guides

Ryze AI — Autonomous Marketing

Put the decisions to work on a live account

  • Connect Google Ads, Meta, GA4 and Search Console
  • Let the agent apply the safe changes
  • Review the rest in one queue
Start free

2,000+

Marketers

$500M+

Ad spend

23

Countries

Ryze AI: marketing on autopilot

free to connect · flat fee

Start free trial
Live results across
2,000+ clients

Paid Ads

Avg. client
ROAS
0x
Revenue
driven
$0M

SEO

Organic
visits driven
0M
Keywords
on page 1
48k+

Websites

Conversion
rate lift
+0%
Time
on site
+0%
Last updated: Sep 18, 2026
All systems ok