▲ | jonasnelle 5 days ago | |||||||
Thanks! We think of the browser as an authoring tool where you create, test and refine skills. After you've done that, the API is great for cases where you want to incorporate Autotab into a larger data flow or product. For instance, say Company A has taught Autotab to migrate their customers' data - so their customers just see a sync button in the Company A product, which kicks off a Autotab run via API. Same for restaurant booking, if you'd want that to happen programatically. | ||||||||
▲ | pacifi30 5 days ago | parent | next [-] | |||||||
Understood! How does it work if we have several different restaurants to order from, do I need to record each ordering session and create skills for each restaurant or it can infer on its own given the task to order from a restaurant. Secondly, any docs or samples to see how to integrate this with your API? | ||||||||
| ||||||||
▲ | handfuloflight 5 days ago | parent | prev [-] | |||||||
Is the API also charged based on runtime? And I'm assuming that workflow happens in the cloud? What if it's behind a login? What if that login requires 2FA? | ||||||||
|