ZV-2026-0642 · 2026-09-02 · livedatalink.ai
livedatalink.ai: Type of mc on carrier_monitor_recheck changed number → number|string.
breaking
What changed
Type of mc on carrier_monitor_recheck changed number → number|string. Type of dot on carrier_monitor_recheck changed number → number|string. Type of dot_numbers on carrier_vetting_batch changed array → unset. Type of mc on carrier_vetting_evidence_pack changed number → number|string. Type of dot on carrier_vetting_evidence_pack changed number → number|string. Type of mc on carrier_vetting_score changed number → number|string. Type of dot on carrier_vetting_score changed number → number|string. Type of mc on load_tender_fraud_shield changed number → number|string. Type of dot on load_tender_fraud_shield changed number → number|string.
What to do
If your agents call livedatalink.ai, 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
− number + number|string carrier_monitor_recheck − number + number|string carrier_monitor_recheck − array + unset carrier_vetting_batch − number + number|string carrier_vetting_evidence_pack − number + number|string carrier_vetting_evidence_pack − number + number|string carrier_vetting_score − number + number|string carrier_vetting_score − number + number|string load_tender_fraud_shield − number + number|string load_tender_fraud_shield