I'm not sure what the benefit of this is over the alexa voice service api:<p><a href="https://developer.amazon.com/public/solutions/alexa/alexa-voice-service/content/avs-api-overview" rel="nofollow">https://developer.amazon.com/public/solutions/alexa/alexa-vo...</a><p>Does anyone know how this differs from alexa voice services? Does this allow you to get away from the stilted "example phrases" of the alexa api and just get a transcript? Judging from the inclusion of "intents" on the faq, it looks like the "example phrase" interface will still be required:<p><a href="https://aws.amazon.com/lex/faqs/" rel="nofollow">https://aws.amazon.com/lex/faqs/</a>
Pricing: <a href="https://aws.amazon.com/lex/pricing/" rel="nofollow">https://aws.amazon.com/lex/pricing/</a><p>>$0.004 per voice request, and $.00075 per text request.<p>I don't know what else to compare this to.
I see how they went from Alexa to Lex, but does anybody else think the only time they've ever heard of Lex is Lex Luther? Is it a great idea to name a product aimed at developers which is boardering in the AI space after Superman's nemesis?<p>I'm not going to forget it as a name. Thoughts?
I won't participate and here is why... I want to delay my disintermediation and assimilation a little longer. At some point, soon, Amazon will displace commerce and the merchant class as we know it and I am not ready to let go yet.