July: field constraints, key analytics, drift alerts · Evlio

Blog
/
Product
/
July: field-level constraints, key-scoped analytics, drift alerts
Product
Jul 1, 2026
·
3
min read · Updated
Aug 27, 2026
July: field-level constraints, key-scoped analytics, drift alerts
Everything that shipped this month, including the schema editor and per-key usage.
TL;DR
Field-level constraints are now editable and propagate to contracts, generated tests, and MCP tool schemas in one publish.
Every usage chart can be scoped to a single API key, separating partners, copilots, and experiments.
Drift alerts post to Slack or any webhook within one sync cycle, tagged breaking, compatible, or cosmetic.
ET
Evlio Team
The Evlio Team
ON THIS PAGE
01
Field-level constraints
02
Key-scoped analytics
03
Drift alerts
04
Also shipped
July's release is about precision. The schema editor now edits constraints at the field level, analytics can be scoped to a single API key, and drift alerts reach you on your own channels before a consumer notices anything. Everything below is live on all plans as of July 1, with no migration required.
Field-level constraints
The schema editor now exposes the constraint layer of every field: numeric bounds, string patterns, enums, formats, and required flags, editable inline with validation against
JSON Schema 2020-12
. Constraints propagate everywhere the field appears, contract views,
generated tests
, and MCP tool schemas, in the same publish. A
quantity
field capped at 1–500 in the editor is now rejected at 501 by your generated tests and described as "1–500" in the tool description an agent reads. Fields edited this way also rescore immediately, so tightening a bare
string
into a bounded enum shows up in the endpoint's agent-readiness grade the moment you save. Constraints are writable over the API as well, so teams that manage schemas in code can treat the editor as a review surface rather than a second source of truth.
Key-scoped analytics
Every usage chart can now be filtered to a single API key: requests, error rate, p95 latency, and token cost per call. This closes the most-requested gap from teams running multiple agents against one server, partner traffic, your support copilot, and an engineer's local experiments no longer blur into one line. Key filters combine with the existing per-tool breakdown, so "which key drove the p95 spike on
search_orders
Tuesday night" is a two-click query instead of a log dive. Keys can be renamed in place now, too, so dashboards read as "ops-agent-prod" rather than a prefix. Exports honor the filter as well: the CSV download and the usage webhook both accept a key parameter, which turns per-partner usage reports from a spreadsheet ritual into a saved query.
Drift alerts
Evlio has always detected drift between your code and your published spec at sync time. As of this month it can tell you without being asked: alerts post to Slack or any webhook within one sync cycle of detection, tagged by severity, breaking, compatible, or cosmetic. Alert rules are per-service, so a breaking drift in
payments
can page while a cosmetic one in a sandbox stays quiet. Quiet hours are respected per rule, and every alert links directly to the diff it describes. Alerts deduplicate per diff, so a flapping sync cannot page twice for the same change, and resolving the drift auto-closes the thread the alert opened.
Also shipped
OpenAPI export now round-trips
x-
extension fields untouched
Catalog search matches path templates, so
/payouts/{id}
is findable as typed
Contract review pages load 2.1× faster on services with 200+ endpoints
MCP server logs stream in the dashboard with a 2-second delay, down from 30
Tool descriptions over 4,000 characters now warn at publish, since agents truncate long descriptions
Contract review pages remember collapsed sections between visits
Fixed: enum members containing
/
no longer break the schema diff view
Fixed: annual invoices now show the billing period in the account's timezone
FAQ
What shipped in Evlio in July 2026?
Field-level schema constraints, analytics scoped to a single API key, and drift alerts that post to Slack or any webhook, tagged by severity.
Do field constraints affect agents?
Yes. Constraints propagate to contract views, generated tests, and MCP tool schemas in the same publish, so the bounds you set are the bounds agents see and tests enforce.
Is a migration required for the July release?
No. Everything is live on all plans as of July 1 with no migration required.
Product
Share:
X
·
LinkedIn
·
Copy link
READ NEXT
Observability
Sep 2
·
9
min
Observability for agent API traffic: what per-agent attribution actually requires
Read →
OpenAPI
Sep 2
·
8
min
OpenAPI spec and API design editor tools, compared
Read →
Testing
Sep 1
·
7
min
API testing tools that generate tests from code, compared
Read →
Ship notes, monthly
One email with what shipped and what we learned. Unsubscribe anytime.
Subscribe
Leave this field empty