Free beta · 50 measured plugin updates

See which WordPress actions a plugin update changes.

Those agent-callable WordPress actions are the plugin's agent contract: the named things an AI agent on a site can ask it to do. An update can add them, remove them or change their shape. This shows which, for 50 updates measured in advance.

50 measured updates — the whole set
WordPress 7.1 · PHP 8.3 Playground runtime
No account, aggregate counts only

Measured plugin update

This does not install the plugin, inspect your site, or say an update is safe. Updates outside this list are not measured yet, and are reported as not measured rather than guessed at.

What this reads: two versions of a plugin booted in an isolated WordPress Playground runtime, and the abilities each one registered. What it cannot see: your site. It records one aggregate counter per day, channel, tool and outcome — no plugin, no version, no address, no identity, no receipt.

What this compares

Each of the 50 updates was installed twice in an isolated WordPress Playground runtime — once at the old version, once at the new — and the abilities each one registered were recorded. The receipt shows what appeared, disappeared or changed between the two, and abstains when either capture was incomplete. A Playground runtime is isolated to the browser with no persistent side effects, so it is a reading about those two builds and not about your installation.

What this adds to staging and rollback

Existing update tools can back up, test and roll back a site. This preflight answers a narrower earlier question: did the WordPress Ability contract visible to agents change between these exact versions? Keep your normal staging, backup and rollback process whatever this receipt says.