It's interesting, seems like a popular space lately (even within YC). Off the top of my head, there's merge.dev, Terra, Kombo, Workato.
Aside from the obvious question of "how are you different/better?" I'm most curious to know why you're going so broad initially. You've got everything from legal to devtools to gaming. Seems like the opposite of a wedge/beachhead approach. Why?
We evaluated most of these (minus Workato) and landed on Nango. Was by far the most flexible and having the source code available was a big plus (vs. the closed-source alternatives). The team is also reactive to feedback in their Slack community, they even added a few new endpoints for us in < 24 hours
The players you mentioned pre-build standard integrations, in specific categories (e.g. HRIS). We build a platform that lets developers build custom integrations, for any API.
We do offer integration "templates", but it's only a way to get started and templates are meant to be extended.
That's also why our catalog of APIs is extensive. Anybody can rapidly add support for any new API and start building custom integrations for it, and share templates with the community.
I was somewhat involved in this project. Can't get into details but there were other factors/efforts not mentioned which allowed us to scale this while reducing cost per recommendation. As someone mentioned, I do believe we benefited from a price drop over time.
Regarding the monthly scale mentioned in article–we are way beyond that now.
A lot of really smart people worked on this and it was fun to watch unfold.
My stack is Ruby on Rails, PostgreSQL, OpenAI APIs. I chose Rails because I'm very fast in it, but I've found the combination of Rails+Sidekiq+ActionCable is really nice for building conversational experiences on the web. If I stick with this, I'll probably need a native iOS app though.
Vendor stack is: GitHub, Heroku (compute), Neon (DB), Loops.so (email), PostHog (analytics), Honeybadger (errors), and Linear.
I built this a couple years ago (now defunct) for the same reason :) The public JSON endpoints on shopify stores make it pretty easy to get the data. You mentioned using Mongo but it sounds expensive. I honestly think you could do this with just elastic or even postgres full text search and save money.
Here's a pro tip + feature you should implement: Shopify has a semi-hidden hack where you can link directly to checkout of a product if you know the variant ID. You could add a BUY NOW button to your site without forcing the user to navigate the original site or checkout flow. Example:
https://hapaboardshop.com/cart/42165521907955
(it also supports quantities and coupon codes)
A word of caution: more products isn't necessarily better. I definitely found there to be a long tail of really bad shopify stores and products. IMO it's better to curate or audit the stores you index–otherwise you risk your site being littered with kitchy t-shirts or drop-shipping garbage.
Thanks for the heads up! I spent some time trying to get the cart route to work. Doesn't seem to be supported anymore (link you sent leads to a 404 page). Tried it with every combination of Product ID, Variant ID, etc. Let me know if you have any ideas on how to get this to work. It would be a great feature to add to Agora.
And I agree on quality over quantity. Writing a script to remove all stores that are shutdown, products that are sold out, and a few other characteristics. Heavily focusing on the search algorithm and data quality now.
I didnt know about the link to checkout. That's a slightly nicer user experience for sure. Still, its confusing for users who want to do more shopping at the same time. I had users who clicked on a number of items, clicked "add to cart" in each one (all different shops), and then couldn't figure out how to checkout on the main site afterwards! Obviously people were looking for a more complete one-stop-shopping experience than I was providing at the time.
I mean a single checkout from multiple shopify stores isn't really possible (at least by 3rd parties)
My hypothesis is that, if you could drive traffic to your site and offer a fast checkout experience, there's probably multiple ways to monetize that. Driving the traffic is the hard part.
Same, and then a few minutes later I got a Slack message from SecOps, LOL. Don't try this on a computer with CrowdStrike software running on it! It gets flagged because to a naive heuristic, the binary is indistinguishable from a virus. It appears to do some kind of magic self-extraction to an executable file in a temporary directory, and then that executable file executes the original file. And the CrowdStrike endpoint security product intercepts the suspicious execve, kills the process, and alerts the security team...
For whatever it's worth, the SHA sum is correct. The killed message is uninformative, looks like what happens when I'm OOM (but I have 64GB RAM of which only 24 is used for anything at the moment).
Could you disable SIP and run `lldb -- $TMPDIR/.ape-1.8 ./llamafile-server-0.1-llava-v1.5-7b-q4` and give me (1) the name of the instruction that's illegal (or its hex value) and (2) the hex address of where that instruction is in memory? You're encouraged to file a GitHub issue about this too. Thanks!
This is really cool and (I think) unlocks an idea I've had for a long time: moviepass for restaurants (aka a new spin on groupon).
I think you could get consumers to subscribe to discounts/deals at nearby restaurants and I think you could get restaurants to offer discounts one-time or during non-peak days/times. I tried to do this in the past using card issuing services (like Stripe's) but it was clunky with debit cards. The ability to do this via credit would make this a lot easier.
It sounds like you want to offer a credit card which I don't believe Pier is doing. It seems like you want something like Ramp for consumer use. I'm not familiar with it, but it seems like Enfuce[0] might be a possible solution.
