MONOVION

Measured, not claimed.

How MONOVION measures the AI model market

MONOVION publishes short, data-driven videos about AI models: which ones got cheaper or more expensive, which ones answer fastest, which ones climbed the leaderboards. Every number in a video comes from the time series described on this page — most of them from our own measurements. This page documents how we collect them and lets you download the raw data.

What this project is. An automated measurement pipeline (internal name: Benchcast) that runs 24/7 on our own server, stores every measurement in an append-only database and turns significant changes into short videos for the YouTube channel MONOVION. The measurement series has been running since 2026-09-10.

What we measure

ProbeScheduleSourceValues
Price probedaily 06:00 UTCPublic model price lists via the OpenRouter models API; cross-checked against models.dev (provider list prices).USD per 1M input / output tokens
Latency probeevery 3 hoursOur own measurement harness: one fixed prompt sent to each model from a fixed server in Berlin, Germany.Time to first token (ms), output speed (tokens/s), availability, HTTP status
Leaderboard probedaily 06:30 UTCLMArena public leaderboard dataset (Hugging Face) and OpenRouter usage rankings.Rank, score, change vs. previous update
Capability probeweekly, MondayModel catalogs and published deprecation schedules.Context window, max output, shutdown dates
Change watcherevery 30 minutesProvider status pages, model catalog changes, official news feeds and deprecation pages.Incidents, new/removed models

The latency probe in detail

Prices and rankings are public — anyone can copy them. Our latency series is not: it only exists because a specific prompt was sent at a specific time from a specific place. This is how it works (probe version v1, frozen — any change gets a new version):

Full probe prompt (v1)
Read the following passage carefully.

Lighthouses have guided sailors for more than two thousand years. The Pharos of Alexandria, completed around 280 BC, stood on a small island at the entrance to the harbour and is thought to have been well over one hundred metres tall. Its fire was kept burning at night, and polished bronze mirrors may have been used to project the light far out to sea. For centuries afterwards, most lighthouses were simple towers with open fires or candles at the top, and their range was limited by weather, smoke and the brightness of the flame.

The eighteenth and nineteenth centuries brought rapid change. Oil lamps with circular wicks produced a steadier and brighter flame, and parabolic reflectors concentrated that light into a beam. In 1822 the French physicist Augustin Fresnel introduced a lens built from concentric rings of glass prisms. The design captured light that earlier systems wasted and bent it into a narrow, powerful beam that could be seen more than twenty nautical miles away. Fresnel lenses were graded into orders by size, and the largest first-order lenses were used on major coastal lights.

Each lighthouse was given a distinctive pattern of flashes, called its characteristic, so that navigators could identify it at night by timing the intervals between flashes. By day, towers were painted with bands, stripes or checks for the same reason. Keepers lived at the stations, often with their families, trimming wicks, cleaning lenses, winding the clockwork that rotated the optics and recording the weather in logbooks. In fog, bells, horns and later sirens gave audible warnings.

During the twentieth century electricity replaced oil, rotating optics were driven by motors, and automatic systems made resident keepers unnecessary. Radio beacons and later satellite navigation reduced the practical importance of lighthouses, yet many remain in service as a backup and as landmarks, and a large number have been preserved as museums.

Task: Write a detailed, continuous essay of at least 400 words that explains how lighthouse technology developed and why each change mattered to sailors. Write in plain prose without lists, headings or bullet points. Do not ask questions and do not stop early.

How the videos are made

Corrections

The measurement database is append-only: values are never edited or deleted. If a measurement turns out to be wrong, a correction is added as a new data point with a new probe version. If a video contains an error, we correct it in the pinned comment and the description.

Raw data (last 90 days, updated daily)

FileContentRows
latency.csvOwn latency probe: TTFT, output speed, availability, HTTP status per model and route372
prices.csvInput/output prices per 1M tokens (OpenRouter models API)1348
leaderboard.csvLMArena ranks/scores and OpenRouter usage ranks2679
provider_uptime.csvProvider uptime as published by OpenRouter639

Data is provided as-is under CC BY 4.0 — please credit "MONOVION". Third-party figures (prices, leaderboards) remain subject to the terms of their original sources.