So I'm a little conflicted here. I feel like it's useful to have this interface for type checking of parse methods, but it's not part of the API surface of the model. The items here also are completely duplicated by our webapi documentation and overlap almost 100% with the docs for the model attributes.
Yeah, I get those arguments for sure. I guess given that these are API data (which I wasn't really thinking about when I wrote this), we can make an exception.