This is really cool. I was initially skeptical about the 'AI' pitch on your page but having played with it I think that should be your number one pitch, particularly on HN.
For people reading: Using FakerJS and any Yaml/Json library it'd be "easy" to mock things like String or Object, but (if I understand correctly) this goes much further and looks at the name of the entry and something something ai and gives you a realistic response.
So a string called 'username' returns a valid name, which is already handy, but it also matches the 'email' field, which is even better. And the name even matches the country (I got an Italian-seeming name with an address in Italy)
I'm impressed, I'll be sharing this with people at work.
Great to see your usage @anitil.
These aren't just static dummy mocks. Beeceptor looks at schema, fields, description, format, datatypes, and then generats a realistic mock responses to match real response.
This is really cool. I was initially skeptical about the 'AI' pitch on your page but having played with it I think that should be your number one pitch, particularly on HN.
For people reading: Using FakerJS and any Yaml/Json library it'd be "easy" to mock things like String or Object, but (if I understand correctly) this goes much further and looks at the name of the entry and something something ai and gives you a realistic response.
So a string called 'username' returns a valid name, which is already handy, but it also matches the 'email' field, which is even better. And the name even matches the country (I got an Italian-seeming name with an address in Italy)
I'm impressed, I'll be sharing this with people at work.
Great to see your usage @anitil. These aren't just static dummy mocks. Beeceptor looks at schema, fields, description, format, datatypes, and then generats a realistic mock responses to match real response.
Tried, the API response is contextual and useful for demos and integration. Can you fetch URL periodically? For any contract drift.