Being a developer who heavily utilizes internal and external APIs, I like the idea of a tool like this, however, I'm really hesitant to run all calls through a single 3rd party. Especially one this green.
The next question I have is, what about auth? It seems like it could get really messy / insecure using something like this.
Seems like a great project to open source and to run on your own hardware.
Another concern of mine is that now you're running all calls to an API through yet another service, increasing latency on potentially frequently-called methods.
It's certainly not for all API calls.
That seems... unsuitable for most non-public apis.
But you can do key mapping: if you pass your key it will transform it to the real one and if not, then it will just return 403.
Although, for the technical audience (and isn't a technical audience the only audience for this product?), actually using the word 'proxy' somewhere might help make it even more clear. Although I could be wrong, maybe I'm not representative, but it would make it clearer for me anyway.
Although if other HN users aren't having that trouble, maybe it's me, not you.
Do you essentially use this as a proxy, where your apps contact it, and it contacts the apis, so it can keep stats on your api use? That's what the three phrases on the home page sort of imply.
But then when I watch the video... it all goes by so fast, but it's giving me the idea that I had it wrong, and it's doing something else (CORS? What would CORS have to do with what I thought it was doing?)
Is it too much to ask for a couple sentences/paragraphs explaining what it does, instead of just a couple words and a video?