predictions and cache

Readme.md

@@ -27,7 +27,7 @@ Interactive command will ask you for the paths and will create a `.dev-translate
 
 ```
 {
-    "apiKey": "4404413a.b16aaa6",
+    "apiKey": "YOUR_API_KEY",
     "localeDir": "locales",
     "inputLanguageFolderName": "en",
     "inputLanguage": "ENUS"
@@ -40,10 +40,26 @@ Then dev-translate CLI will translate all the json files from input Language and
 
 For example if you have a folder `./locales/` with `en` , `pl`. `de`, `fr`, `in` and you choose `en` as an input language. Dev translate will automatically translate from `en` to all other langauges keeping the json file structure.
 
+## Predict translation cost
+
+As translations consume tokens from API you can easily predict translation cost of your locale folder by running:
+
+```sh
+dev-translate predict
+```
+
 ## Cache
 
 Dev-translate backend includes cache inside it so we don't need to implement local cache here
 
+### Clear Account cache
+
+If you want to clear your cache not to reuse cached translations anymore:
+
+```sh
+dev-translate clear
+```
+
 ## Beta
 
 CLI is the part of beta stage of new dev-translate and it is not yet on https://devtranslate.app. Contact support at [email protected] for early access.
@@ -60,4 +76,6 @@ $ npm run start
 ## Roadmap
 
 - [ ] support XML files in CLI
-- [x] support JSON files in CLI
+- [x] support JSON files in CLI
+- [x] support predictions
+- [x] support cache clear