Creating a text analyser: import, export and API

One of the main reasons why I started making my own text analyser instead of using already available ones is the ability to import and export tasks + a clear API sharpened for mass generation.

Why import and export?

I want the trivial ability to load a table with a hundred rows, where each row is a separate job, click a button and go to sleep, saving myself hours on, ahem, drevidentI want to click on the «Download all» button and get 1 table where each row will have 1 separate ToR. And after that I want to click "Download all" and get also 1 table, where in each line will be 1 separate ToR, which I can already drive into the agent and generate at once on this list of a hundred texts, well or the old-fashioned way to give this table to a copywriter, so that he just followed it and wrote texts. And, of course, not to lose the opportunity to download individual uploads in an archive.

Why do you need an API?

To quote Tsoi here:

In an interview Viktor Tsoi gave in Perm in 1990, when asked about his favourite toy as a child, he replied: «Plasticine». To the next question about what he made out of it, Tsoi said: «Everything.».

No kidding, when you make agent systems, and in general you want to automate something properly, you need API, so that you don't have to make the same modules for different clients and for yourself every time.