Gemini Decisions API

API docs: <a href="https:&#x2F;&#x2F;aistudio.google.com&#x2F;docs&#x2F;decisions-api" rel="nofollow">https:&#x2F;&#x2F;aistudio.google.com&#x2F;docs&#x2F;decisions-api</a>

I&#x27;m sort of surprised it took Jev for everyone to realize &quot;oh yeah, this is a useful thing that we should have in our product portfolio&quot;.<p>But maybe this is one of those things that&#x27;s only obvious in retrospect? I&#x27;m sure people were trying something similar years ago with grammar-constrained outputs (for example to only output a simple json structure), but you can&#x27;t get probabilities out of the model that way. Which makes me wonder: how <i>do</i> these models calculate probabilities?

Its bit more expensive than other other Decision Models in the same lane.<p>However, it can accept Audio and Video as input as well and for those specific cases it can be extremely useful.

Looks like Google announced their own Jev inspired API and model

Meanwhile, they are suffocating Jules today (<a href="https:&#x2F;&#x2F;killedbygoogle.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;killedbygoogle.com&#x2F;</a>) with a metaphorical pillow to the face and no migration path mapped out for casual users apart from &quot;use antigravity&quot; in a 1 line high banner; after about a year of existence.<p>It seems unlikely this will be around in 6 months at this rate.

It took OpenAI 2 weeks after Jev to release a decision end point, and now google does it 2 months later. Why such a difference? Bureaucracy? Quality control?