Yeah that would work. But yes, when exploring a new API this is exactly why I didn't make this mandatory. Sometimes creating model versions of an API is just unreasonable IMHO, that's part of the original intended simplicity of this plugin. I think it may have strayed from that idealism however.

Originally I wanted to make the amount of effort required to add new APIs as ridiculously easy as creating a new array. There is also something that can be said about digesting apiary or other services that document apis. I don't like enforcing that people must scaffold out a bunch of models and relationships before they can start digesting an API, it means I'm expending just as much effort as I would have if I imported a pre-existing lib or CakePHP lib for said API.