
Vida Wants To Bill for AI Agents by Results Rather Than Usage
Usage-based billing aligns the vendor's revenue with the agent taking longer. Outcome pricing inverts that.
Category
327 articles

Usage-based billing aligns the vendor's revenue with the agent taking longer. Outcome pricing inverts that.

Support systems spent decades modeling human behavior. Now some fraction of incoming requests are machines acting for people.

An advertiser does not need a model that renders a documentary. It needs one where the product looks right and the person does not morph mid-sentence.

The interesting metric has moved from total parameters to active parameters, and the memory bill did not move with it.

Generating plausible motion is solved enough that the interesting work has moved elsewhere, and the unsatisfying part has been the audio.

The engines are close enough now that the invoice is a better guide than the leaderboard.

Adding parameters still works. The more active work is about making a given model do more with less.

Quality converged, and the competition moved to where the model runs, how fast it starts, and what it costs per call.

A thousand agents that each need supervision multiply the supervision, not the capacity.

Agent capability stopped being the headline. The headline is whether a company can prove, after the fact, exactly what its agent did.

The roster is the least interesting part. The runtime underneath it changes what an agent is for.

An agent that runs unattended is an agent that can run up a bill unattended. North 2 makes the budget part of the product.