> A regular api poorly implemented will have all the same cons and none of the pros.

Okay, so don't make a poorly implemented one?

Also, no, it kind of won't. Let's look at what they are again

.

"It is actually a pain to use"

Not an API characteristic

.

"you'll have to manage two or more type systems if there are no code first generates in your language"

Not an API characteristic

.

"It doesn't support map/tables/dictionaries."

Not an API characteristic

.

"No clear path for Api versioning"

Not an API characteristic

.

Looks like it's actually zero for four