If you think about the customer journey as Research-Evaluate-Purchase, the 30 day free trial is the Evaluate stage. There isn't enough information (or any specifics) on the landing page to do any meaningful amount of research.
The "It's so bad it's good" effect?
nginx/1.13.3
It's targeted for any REST/Json based api. (reading or writing)
At the very least I'd need a comparison with a more mature system like https://www.mulesoft.com/
What is the documentation in for example? RAML? Swagger? HTML?
$20/month is a bit much for a side project. For a real world project, the price is peanuts if the benefits are there, but the lack of explanation makes it a non-starter for many companies, I would imagine.
Luckily, most of that seems to be marketing and documentation, which shouldn't be too difficult to update, if the product is working correctly at least.
Are you actually hosting the API I'd be building? Or just generating boilerplate code for it? Maybe I'm just misunderstanding :)
1) allow non-json responses 2) why would I do pass-thru? for metrics? 3) add test data generation features for mock responses 4) add at least limited scripting features for both pass-thru and mock
Looks like a good start to me and I was not particularly bothered by the current sign up.
I'd put some time into showing some examples of what exactly the service is and how it works. What problem does it solve specifically?
That said, clearly standardization is coming to the world of APIs, and code reuse/generation along with it. Have you looked at Django REST framework? They have a pretty good approach. http://www.django-rest-framework.org/
