ZV-2026-0585 · 2026-09-01 · 402signal.com

402signal.com: miss_reason on preview narrowed to a closed enum (no_candidates, no_402_envelope, no_payto, reachable_200, probe_timeout, quote_expired, invalid_need, upstream_5xx, ssrf, no_input_schem

breaking

What changed

miss_reason on preview narrowed to a closed enum (no_candidates, no_402_envelope, no_payto, reachable_200, probe_timeout, quote_expired, invalid_need, upstream_5xx, ssrf, no_input_schema, constraints_unmet, probe_budget_exhausted, probe_limit_reached, unsafe_to_probe, null); previously valid values may now be rejected. miss_reason on validate narrowed to a closed enum (no_candidates, no_402_envelope, no_payto, reachable_200, probe_timeout, quote_expired, invalid_need, upstream_5xx, ssrf, no_input_schema, constraints_unmet, probe_budget_exhausted, probe_limit_reached, unsafe_to_probe, null); previously valid values may now be rejected.

What to do

If your agents call 402signal.com, pin the new snapshot, patch the affected call sites, and let a green contract check confirm the fix. If you don't use the changed tools, nothing is required, but the rest of the ecosystem just learned about it at the same moment you did.

The redline

−  open
+  enum[no_candidates,no_402_envelope,no_payto,reachable_200,probe_timeout,quote_expired,inva…   preview
−  open
+  enum[no_candidates,no_402_envelope,no_payto,reachable_200,probe_timeout,quote_expired,inva…   validate
+  accept_payTo_change  Optional field accept_payTo_change was added to route; may shift model behaviour.
+  require_transparency  Optional field require_transparency was added to route; may shift model behaviour.
+  pq_trust  Field pq_trust was added to route output.
+  miss_reason  Enum value null added to miss_reason on route.
−  need  Field need on route is no longer required.
Full 402signal.com changelog →JSON feedWatch this for my agents