Many EB/API talking.
So my purpose here is trying to summarize:
Application Programming Interface (API)
1 - It would be like you doing the actions (follow/like/comment/like comment/comment/view story) via your mobile app.
2 - It would require less of your VPS to perform the actions.
3 - In Jarvee you could perform all actions via API.
4 - You could easily get “fake follow/like block”.
5 - IG maybe knows that are software bots (maybe due to the way it scroll / tap)
Embedded Browser (EB)
1 - It would be like you doing the actions (follow/like/comment) via your browser (safari, chrome, firefox …).
2 - It would require more of your VPS to perform the actions.
3 - In Jarvee you could perform just follow/like/comment via EB.
4 - You should not get "fake follow/like block"
5 - IG maybe knows that are a software bot because it leaves “fingerprints” (I will not explain it because I am not sure about it)
WHAT SHOULD I USE?
OPTION 1 - Perform the actions via only API Pros:
-Less of your VPS will be required.
-You would be able to perform all the possible actions via just one “way of communication”. Cons:
-You will probably not be able to complete all your daily actions. because you could easily get "fake follow/like block"
-IG maybe will know that you are using software bot via just one “way of communication”.
OPTION 2 - Perform the actions via API and if it is blocked do them via EB Pros:
-You will probably be able to complete all your daily actions. Cons:
-You could be performing actions via two “ways of communication”. It is not “human like” at all.
— EB would follow, like and comment. (if API is “fake blocked”)
— API would be doing the rest.
-IG maybe will know that you are using software bot via two “ways of communication”.
OPTION 3 - Perform the actions via only EB Pros:
-You will probably be able to complete all your daily actions.
-You would be able to perform all the possible actions via just one “way of communication”. Cons:
-More of your VPS will be required.
fake follow/like block = the block will appear in Jarvee`s software and Jarvee will not perform more actions, but it will not be a “real block” in most of the cases because you can do the actions via your mobile {real API}
real block = when you try to perform an action via mobile/browser and you cannot do it (sometimes a Block Action Message will appear, sometimes you will just click in the follow button and nothing will happen in the background {so you would never had followed that user})
Of course, but maybe if you are getting scraping problems and you are not being able to follow the amount you want, the reason could be the lack of performance due to be doing the actions via EB and consuming a lot of the VPS.
And my 2 cents would be once it gets blocked, it doesn’t really know how to get out of it, and it keeps going in loops. That’s why it can’t do actions but manually your able to from a browser og mobile app.
But realise when clearing cookie, it works. Maybe because you kind of remove this glitch, which might be causing the tool to go into looping and ending up in a fake block in the end.
Exactly until the next glitch happens. It gets stuck you get fake blocked again, you clear cookies and move on!
BUT, as you mention, clearing cookies is a temp solution for NOW, and no one really knows the consequences for clearing cookies and keep pushing the accounts would be on long term.
That’s why some agencies stopped botting and switched to ads or normal growth, botting is great but with the time AI is fully constructed it will be hard. If we have this problems and AI is a little baby imagine in the future
I think that IG automation still have a long way to go and all these agencies that are stopping is just giving us (the ones that persist) more room to work.
New people will not ask as many questions as you like and open new threads 
IG is working hard to get rid of automation and panels.