36 comments

[ 2.7 ms ] story [ 55.4 ms ] thread
Needs an Agent skill! Gotta be more modern :)
I like how you spent $10 for the domain for this. :)
Bug report: I entered 3 + 4 and did not get a kinda or true.

This app is ngmi

Vulnerable to a distillation attack, unfortunately not much of a moat.
7.0000000000000001 evaluates to true.
I will vibe code my way out of poverty:
(comment deleted)
Enterprise looks promising, but before I take this to upper management: How many sevens of uptime are we talking?
This SaaS actually will be replaced with an in house vibecoded solution.
Does this have an MCP server?
I can use this as a random number generator; at least it's not nine.
Heads up OP: I’m trying to get a pro license but your checkout flow is borked. Probably should fix ASAP before missing out on HN front page traffic.
Apparently “seven” is only kinda seven. I would argue that seven is seven!
Bug report: I tried 6.999999̅ and got false. So there's some nonstandard model of the reals being leveraged here.
That documentation is woefully inadequate. It provides only one example request, and then it shows two separate responses, and it doesn't make clear which one is associated with the request. It doesn't even describe the individual request fields, nor does it provide any response codes or a list of error codes/messages. How am I supposed to develop with this?

I do, however, appreciate the seven figure SLA. My service requires at least five nines of uptime, and seven figures is definitely more than five.

I misread this as "is even" and was shocked that 46 returned false
complaint: someone entered "seven" and it crashed my entire infrastructure because the output returned a non standard 'kinda'.
It hallucinates 6.9999999999999996 to be seven.
No other numbers were harmed in the making of this API.

But their feeling hurts, especially primes.

This Is Seven as a Service.
I wanted to subscribe and I can't! How do you expect to make any money if that doesn't work?!!1