monit.rs · Zenofex LLC
Blog
Data-driven writing about API stability, schema drift, and the kinds of production regressions our monitors catch. Reports, analysis, and dispatches from the monit.rs team.
Published posts
- Four public APIs have not changed a byte since July, and GitLab shipped 12 spec revisions without breaking anything
Published 2026-11-08
Eleven of the 44 public APIs we score shipped zero breaking changes in 90 days, and four have published a byte-identical OpenAPI document since July — verified by re-fetching and comparing SHA-256. Th - The field that was removed eleven times: 62% of the breaking changes we count come from flapping specs
Published 2026-11-07
PostHog's spec "removed" the field id in eleven separate weekly snapshots; Vercel added a oneOf variant in 17 of 18. Seven vendors account for 62% of every breaking change we counted in 90 days, and t - The October API drift report: one week, 526 breaking changes, and 78% of them were previously invisible
Published 2026-10-08
One weekly sweep across 32 public APIs found 1,008 breaking findings, 526 distinct vendor actions, and 78% of them inside shared $ref'd schemas our engine could not see until last week. OpenAI made 62 - The September API drift report, corrected: we were counting the wrong thing
Published 2026-10-04
We found three defects in our own diff engine and re-ran September: 313 breaking changes became 1,905. But those are findings, not changes — the real figure is 248 distinct vendor actions, and it inve - Why every stability score on monit.rs changed today
Published 2026-09-27
Our API-stability score rewarded batching breaking changes and missed their size. Deepgram was about to be named worst offender for a spec cleanup, not a break. The fix, and every corrected score. - The anatomy of an API break: 920 events, three findings the taxonomy makes uncomfortable
Published 2026-08-30
920 breaking OpenAPI changes across 47 public APIs in 35 days, grouped by kind. Two-thirds are the same event type; the required/optional flag drives most of the ambiguity; two vendors account for 96% - Corrected: Stripe, OpenAI and GitHub did break clients last quarter. PlanetScale didn't.
Published 2026-08-24
We claimed these four APIs shipped zero breaking changes. Our engine could not see inside $ref'd schemas. Re-measured: Stripe made 12 breaking changes, OpenAI 20, GitHub 7, PlanetScale 0. The patterns - 31 of 36 public APIs shipped zero breaking changes this quarter. Here are the five that didn't.
Published 2026-08-24
A 90-day stability leaderboard of 36 tracked public APIs — Stripe, GitHub, Cloudflare, OpenAI, Datadog, and 31 others. Five vendors ship real breakage; OpenAI ships 164 non-breaking additions with zer - Five OpenAPI breaks from August, and one that only looked like a break
Published 2026-08-20
Five OpenAPI breaks from August across Cloudflare, Supabase, DigitalOcean, PostHog, and Vercel. Two weren't in the vendor changelog; one wasn't a real break. - The great API drift report: what 3 weeks of monitoring 28 public APIs actually caught
Published 2026-08-13
345 flagged breaking changes across 28 public APIs (Stripe, Cloudflare, Vercel, GitHub, Supabase, OpenAI) over 3 weeks. What status-code monitors miss.
What monit.rs does
monit.rs compares observed response fields and types with a learned
baseline. Run OpenAPI contract checks against the latest stored response
when you want to compare the implementation with a declared contract.
See the difference when a field disappears or changes type. Optional
AI summaries suggest possible causes and next steps; review the evidence
before accepting a new baseline.
What you get on the free tier
- Monitor 3 endpoints, full feature set, no credit card
- Schema-aware regression detection — catches missing fields, type drift, new properties, status shifts
- OpenAPI contract testing — validate the latest stored response on demand
- Optional AI summaries — suggested causes and next steps alongside the observed diff
- Public status pages at <slug>.status.monit.rs — share uptime history with customers
- Multi-channel alerts — email, Slack, Discord, PagerDuty, webhook
- Security fuzz testing — AI-generated adversarial edge-case tests to surface input validation gaps
- MCP server for Claude Desktop / Cursor / Cline (no auth, three tools)
How it works
- Add your endpoint. Paste a URL. Set method + auth. Done.
- Baseline learned. monit.rs probes your endpoint and records the expected schema, types, and structure automatically.
- Regressions caught. Review detected changes and send a test alert to confirm your notification destination.
Public API changelog surface
monit.rs also runs a public changelog of 47+ well-known API
vendors (Stripe, GitHub, OpenAI, Cloudflare, Datadog, PostHog,
Vercel, Supabase, and 39 more). Every detected OpenAPI change
is published at
/changelog
with per-vendor RSS feeds, stability badges, and side-by-side
comparison pages.
See how we compare with existing monitors:
vs Pingdom ·
vs Checkly ·
vs Uptime Robot ·
vs Statuspage.io ·
vs Bump.sh ·
vs Optic ·
vs Postman Monitors