Show HN: I built a free oEmbed API for the web
oembed.io
oembed.io
oEmbed is a standard, therefore you're not locking anyone into your platform by making it free now and charging later. If they don't like the price, they can just switch back to Emed.ly or some other provider.
oEmbed is a standard, and I really think there are a lot of cool things that can be done with it given the opportunity. Currently, the API is not rate limited, but this may be something I will have to look into in the future (I have only load tested up to 250req/sec). I will be adding a TOS in the few weeks.
Where I do plan on charging, is expanding the api to include a "kitchen sink" where I include all data that I can possible grab from a URL. I think this will add real value to the API, and I will end up charging for it once it is finished (probably a few months down the road).
oEmbed.io will always be free. If you want to pay or don't like my conditions, then you can go use embed.ly. But I genuinely feel like this is a contribution I am willing to make to the community.
Hopefully that sheds a little more light on where my head is at with this!
I submitted a few patches concerning HTML parsing, Google Maps, OpenStreetMap, Magnatune.com, OCReMix.org, Firefox Marketplace, Tindeck.com (and a few tiny bugfixes).
A quick clarification: #1: our endpoint is "community" one. It's free and open for dev purposes, but it's not suggested for production use as one can easily self-host it (though we use same server for number of heavy traffic apps like Iframely for Gmail chrome ext).
#2: Iframely now has the oEmbed endpoint too. We trim much richer infos into oembed format for backwards compatibility.
Thanks!
Again, if you need it short term -- don't hesitate to reach out!
In our service we're oembedding external content but we're a bit frustrated as often things stop working and maintaining the js library is an extra effort.
I spoke with the author of [1], but he was not really into using 3rd party services...
If you let me know your email, I will be sure to reach out to you once it is finished!
If you have any other ideas, let me know! :)
I think also a server-side library would be useful. You might think to use a service like Mashape to avoid the problem of choosing a language.
Edit: oh, and mobile. We're having a lot of troubles replicating the same embed experience on iOS (and I have no experience on android/windows phone, so I assume the worse ;)
I will make a better inspector so you can interactively see what is being sent, and what you are getting back :)