Human error is an issue that we're always tackling. First, we're hiring a really high quality team so we're minimizing error from the start. Beyond that, we have a review system in place for the human responses, to ensure that the results are accurate.
This is something that we're always looking to improve and are always building tooling to solve.
For one, as a company, we're fully focused on our API (whereas Fancy Hands is primarily focused on the consumer assistant product). That means they're less willing and agile to help developers, learn about their use cases, or support them as they scale.
Another large differentiator is FancyHands has often been too expensive to scale with companies as they grow, and aren't focused on building the tooling necessary to make large-scale operations possible.
I think this idea is really on point. But honestly I felt a little bit freaked out with the tagline 'API for Human Labour', might just be the luddite in me though.
For now, there are a couple main differences:
* High quality team members we personally vet (vs. the crowdsource model)
* Significantly simpler API
* We build all the tooling for our team members ensuring they complete things efficiently.
* Realtime responses, even for low volume
14 comments
[ 3.4 ms ] story [ 41.1 ms ] threadIf you have any uses cases in your company or just as a developer, please email me at alex@scaleapi.com and I'm happy to chat.
I'm also here to answer any questions you have :)
As someone who once struggled extensively to use AMT, I think the need here is genuine and I'm glad to see someone doing it right.
This is something that we're always looking to improve and are always building tooling to solve.
Another large differentiator is FancyHands has often been too expensive to scale with companies as they grow, and aren't focused on building the tooling necessary to make large-scale operations possible.
How is this different from Crowdflower? https://www.crowdflower.com
For now, there are a couple main differences: * High quality team members we personally vet (vs. the crowdsource model) * Significantly simpler API * We build all the tooling for our team members ensuring they complete things efficiently. * Realtime responses, even for low volume