{"id":25684700,"url":"https://github.com/kudzaiprichard/coin-compass","last_synced_at":"2026-04-10T11:02:23.843Z","repository":{"id":246065330,"uuid":"760105922","full_name":"kudzaiprichard/coin-compass","owner":"kudzaiprichard","description":"A microservice API for predicting cryptocurrency via machine learning model","archived":false,"fork":false,"pushed_at":"2024-06-25T15:42:43.000Z","size":6305,"stargazers_count":3,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-02-24T17:41:16.659Z","etag":null,"topics":["binance","binance-api","cryptocurrency","flask","jason-web-tokens","java","machine-learning","microservice","pandas","python","sckit-learn","seaborn","sklearn","springboot","zipkin","zipkin-sleuth"],"latest_commit_sha":null,"homepage":"","language":"Jupyter Notebook","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/kudzaiprichard.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2024-02-19T19:48:31.000Z","updated_at":"2024-06-25T17:14:40.000Z","dependencies_parsed_at":"2024-06-25T17:32:55.864Z","dependency_job_id":"34cada24-5f1e-413a-886f-072cd9604679","html_url":"https://github.com/kudzaiprichard/coin-compass","commit_stats":null,"previous_names":["kudzaiprichard/coin-compass"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/kudzaiprichard/coin-compass","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kudzaiprichard%2Fcoin-compass","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kudzaiprichard%2Fcoin-compass/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kudzaiprichard%2Fcoin-compass/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kudzaiprichard%2Fcoin-compass/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/kudzaiprichard","download_url":"https://codeload.github.com/kudzaiprichard/coin-compass/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kudzaiprichard%2Fcoin-compass/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":31639524,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-10T07:40:12.752Z","status":"ssl_error","status_checked_at":"2026-04-10T07:40:11.664Z","response_time":98,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["binance","binance-api","cryptocurrency","flask","jason-web-tokens","java","machine-learning","microservice","pandas","python","sckit-learn","seaborn","sklearn","springboot","zipkin","zipkin-sleuth"],"created_at":"2025-02-24T17:32:29.955Z","updated_at":"2026-04-10T11:02:23.820Z","avatar_url":"https://github.com/kudzaiprichard.png","language":"Jupyter Notebook","funding_links":[],"categories":[],"sub_categories":[],"readme":"\n\u003ca name=\"readme-top\"\u003e\u003c/a\u003e\n\n\u003c!-- PROJECT LOGO --\u003e\n\u003cbr /\u003e\n\u003cdiv align=\"center\"\u003e\n  \u003ca href=\"https://github.com/kudzaiprichard/realestate-backend\"\u003e\n    \u003cimg src=\"res/logo.svg\" alt=\"Logo\" width=\"150\"\u003e\n  \u003c/a\u003e\n\n  \u003ch3 align=\"center\"\u003eCoin Compass Microservice Api\u003c/h3\u003e\n\n  \u003cp align=\"center\"\u003e\n    A microservice api for predicting cryptocurrency prices via machine learning\n    \u003cbr/\u003e\n  \u003c/p\u003e\n  \u003cbr/\u003e\n\u003c/div\u003e\n\n\u003c!-- TABLE OF CONTENTS --\u003e\n\u003cdetails\u003e\n  \u003csummary\u003eTable of Contents\u003c/summary\u003e\n  \u003col\u003e\n    \u003cli\u003e\n      \u003ca href=\"#about-the-project\"\u003eAbout The Project\u003c/a\u003e\n      \u003cul\u003e\n        \u003cli\u003e\u003ca href=\"#project-scope\"\u003eProject Scope\u003c/a\u003e\u003c/li\u003e\n        \u003cli\u003e\u003ca href=\"#project-design\"\u003eProject Design\u003c/a\u003e\u003c/li\u003e\n         \u003cul\u003e\n            \u003cli\u003e\u003ca href=\"#api-gateway\"\u003eApi Gateway\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#auth-service\"\u003eAuth Service\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#config-service\"\u003eConfig Service\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#crypto-service\"\u003eCrypto Service\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#favorite-service\"\u003eFavorite Service\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#predict-service\"\u003ePredict Service\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#profile-service\"\u003eProfile Service\u003c/a\u003e\u003c/li\u003e\n            \u003cli\u003e\u003ca href=\"#service-registry\"\u003eService Registry\u003c/a\u003e\u003c/li\u003e\n         \u003c/ul\u003e\n         \u003cli\u003e\u003ca href=\"#machine-learning-model\"\u003eMachine Learning Model\u003c/a\u003e\u003c/li\u003e\n        \u003cli\u003e\u003ca href=\"#built-with\"\u003eBuilt With\u003c/a\u003e\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/li\u003e\n    \u003cli\u003e\n      \u003ca href=\"#getting-started\"\u003eGetting Started\u003c/a\u003e\n      \u003cul\u003e\n        \u003cli\u003e\u003ca href=\"#prerequisites\"\u003ePrerequisites\u003c/a\u003e\u003c/li\u003e\n        \u003cli\u003e\u003ca href=\"#installation\"\u003eInstallation\u003c/a\u003e\u003c/li\u003e\n        \u003cli\u003e\u003ca href=\"#contributing\"\u003eContributing\u003c/a\u003e\u003c/li\u003e\n      \u003c/ul\u003e\n    \u003c/li\u003e\n    \u003cli\u003e\u003ca href=\"#license\"\u003eLicense\u003c/a\u003e\u003c/li\u003e\n    \u003cli\u003e\u003ca href=\"#contact\"\u003eContact\u003c/a\u003e\u003c/li\u003e\n    \u003cli\u003e\u003ca href=\"#acknowledgments\"\u003eAcknowledgments\u003c/a\u003e\u003c/li\u003e\n  \u003c/ol\u003e\n\u003c/details\u003e\n\n\u003c!-- ABOUT THE PROJECT --\u003e\n# About The Project\n\n### Project Scope\n\nProject Description: Coin Compass is a microservice project designed to predict cryptocurrency prices \nusing machine learning algorithms. It will integrate with various cryptocurrency data sources and leverage machine learning \nmodels to generate price forecasts for different time horizons.\n\n#### Project Objectives:\n\n* Develop a machine learning model capable of predicting cryptocurrency prices with acceptable accuracy.\n* Design and implement a microservice architecture for real-time and efficient prediction delivery.\n* Integrate with relevant cryptocurrency data sources to ensure access to historical and current market data.\n* Provide an API for easy integration with other applications and platforms.\n* Offer customizable prediction options based on user-defined parameters.\n\n\n## Project Design\n\n### Architecture\nSystem uses a Microservice architecture. `But what are a Microservice?`\n\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/Microservices-architecture-works.jpg\" alt=\"architecture Diagram\" \u003e\n\u003c/div\u003e\n\nA system is usually built in a Microservice or in a Monolith architecture manner.\n\n#### Microservice\nThe microservice architecture, is a way of developing software that breaks down a large application into smaller, \nindependent services. Each service has its own specific function and communicates with other services through well-defined \ninterfaces, typically APIs. Here's a breakdown of the key characteristics:\n\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/Monolithic-architecture-Vs.-Microservices-architecture.jpg\" alt=\"architecture Diagram\" \u003e\n\u003c/div\u003e\n\n### Monolith \nThis describes a single, unified software application containing all the features and functionalities within itself. \nThink of it as a large building with everything under one roof. It's typically self-contained and independent from other\napplications. While simple to understand and manage initially, monolithic applications can become cumbersome and challenging \nto maintain and scale as they grow in complexity.\n\n### Characteristics of a Microservice\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/characteristics.png\" alt=\"architecture Diagram\" \u003e\n\u003c/div\u003e\n\n* `Split into numerous components` : Instead of a single large application, the system is divided into independent, \nsmall services each performing a specific task. These services communicate through well-defined APIs\n\n* `Robust and resistant to failure` : Each service is designed to be isolated and self-contained, minimizing the impact \nof failures on the whole system.\n\n* `Simple routing process` : The system utilizes a clear and efficient mechanism for directing requests to the appropriate \nservice. This could involve API gateways, service meshes, or other routing strategies.\n* \n* `Decentralized operations` : Each service can be managed and deployed independently, allowing for different teams and technologies to be used.\n\n* `Built for morden business` : Microservices architecture aligns well with the flexible, dynamic, and scalable needs of modern businesses.\n\n\n## Services\nThe fundamental building blocks of the entire system comprises 8 microservices with each services managing a particular task\nbelow each service explained \n\n\n## Api Gateway\nan API Gateway acts as the \"front door\" to your system, mediating the flow of requests between clients \n(like mobile apps or websites) and your various backend services.\n\n* `Single entry point`: Clients interact with the API Gateway using a single, well-defined API instead of needing to know and connect to individual services directly. This simplifies client development and integration.\n* `Traffic routing`: The API Gateway receives requests, identifies the appropriate target service based on defined rules (e.g., URL, headers), and routes the request accordingly.\n* `Protocol translation`: It can act as a translator between different protocols used by clients and services, ensuring seamless communication despite variations.\n* `Security enforcement`: The API Gateway can implement security policies, throttling, and authentication/authorization checks before forwarding requests to services, enhancing overall system security.\n* `Monitoring and analytics`: It can collect and analyze data about incoming requests and responses, providing insights into API usage and system performance.\n\n#### Api Endpoints\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/api-gateway-endpoints.png\" alt=\"endpoints\" \u003e\n\u003c/div\u003e\n\n### Auth Service\nAn Auth Service utilizing JWT (JSON Web Token) for role-based security plays a crucial role in managing user access \nand authorization. Here's a breakdown of its functionalities and considerations:\n\n* `User registration and authentication`: Provides secure user registration and login options, potentially integrating with social media logins.\n* `JWT token generation`: Upon successful authentication, generates a signed JWT token containing user information and assigned roles.\n* `Token validation`: Validates incoming JWT tokens from other services, verifying their authenticity and expiration.\n* `Role-based access control (RBAC)`: Associates user roles with specific permissions and enforces access restrictions based on these roles.\n* `Token refresh`: Offers mechanisms to refresh expiring tokens without requiring users to re-authenticate.\n\n#### Api Endpoints\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/auth-service-endpoints.png\" alt=\"endpoints\" \u003e\n\u003c/div\u003e\n\n## Config Service\nA Config Service acts as a central repository for all configuration settings needed by your individual services. \nThis approach offers several advantages over hardcoding configurations within each service, leading to better\nmaintainability, flexibility, and centralized control.\n\n* `Configuration storage`: Securely stores configuration data for various aspects of your services, including API keys, database connections, logging levels, feature flags, and other environment-specific settings.\n* `Dynamic configuration updates`: Allows updating configurations without requiring individual service deployments, improving agility and reducing downtime.\n* `Versioning and rollbacks`: Supports configuration versioning and rollback capabilities to enable reverting to previous configurations if needed.\n* `Access control and security`: Implements access control mechanisms to restrict who can modify configurations and ensures secure access to sensitive data.\n\n## Crypto Service\nA Crypto Service responsible for connecting to Binance and retrieving real-time candlestick data plays a crucial role \nin generating timely predictions. Here's a breakdown of its functionalities and considerations:\n\n* `Connection establishment`: Securely connects to the Binance API using appropriate authentication and authorization mechanisms.\n* `Data retrieval`: Fetches real-time candlestick data for desired cryptocurrencies and timeframes specified by the system or user requests.\n* `Data filtering and pre-processing`: Cleans and filters the raw data to ensure consistency and suitability for further processing.\n\n#### Api Endpoints\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/auth-service-endpoints.png\" alt=\"endpoints\" \u003e\n\u003c/div\u003e\n\n## Favorite Service\nA Favorite Service in your Coin Compass project could act as a bookmarking system for users to keep track of \ntheir preferred cryptocurrencies. Here's how it might function:\n\n* `Adding favorites`: Users can add cryptocurrencies to their personal list of favorites, potentially through an API or user interface.\n* `Managing favorites`: Users can view, edit, or remove entries from their favorite list.\n\n#### Api Endpoints\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/auth-service-endpoints.png\" alt=\"endpoints\" \u003e\n\u003c/div\u003e\n\n## Predict Service\nA Predict Service that takes crypto candle sticks and predicts price is a key component of your envisioned \nCoin Compass project. Here's a breakdown of its potential functionalities and considerations:\n\n* `Data input`: Receives cryptocurrency candlestick data as input, which typically includes information like opening and closing prices, high and low prices, and trading volume for a specific timeframe.\n* `Model access`: Accesses and utilizes a trained machine learning model specializing in cryptocurrency price prediction.\n* `Prediction generation`: Based on the input data and the trained model, generates price predictions for a specified future timeframe.\n* `Customization`: Might offer options to customize predictions based on different parameters like prediction horizon, technical indicators, or specific cryptocurrencies.\n* `Output format`: Outputs the generated predictions in a structured format, potentially including confidence scores or prediction ranges.\n\n#### Api Endpoints\nComprises a single POST endpoint - `api/v1/predict`\n\n### Machine Learning model\n## Usage\nTo use this project, simply run the crypto.py script:\n\npython crypto.py\nThis will load the data, train the model, and generate the predicted vs actual volume graph.\n\n## Dataset\nThe dataset used in this project is the Cryptocurrency Historical Prices dataset, which contains historical prices for various cryptocurrencies.\nDataset source here  https://www.kaggle.com/datasets/sudalairajkumar/cryptocurrencypricehistory?resource=download\n\n#### Model\nThe supervised learning model used in this project is the Linear Regression model from the Scikit-learn library. This model is trained on the previous cryptocurrency volume data to predict the future volume.\n\n#### Graph\nThe graph shows the predicted volume vs the actual volume for the cryptocurrency. This graph is generated using the Matplotlib library.\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/graph.png\" alt=\"graph\" \u003e\n\u003c/div\u003e\n\n* Second graph out put\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/graph2.png\" alt=\"graph\" \u003e\n\u003c/div\u003e\n\n#### Profile Service\nA Profile Service specifically designed to manage user data like name, date of birth (DOB), \nand other personal information would typically handle the following functionalities:\n\n#### Data management:\n* `Storing user data`: It securely stores user information like names, addresses, DOBs, contact details, preferences, and other relevant data based on the application's requirements.\n* `Data access and updates`: Provides controlled access to authorized users or applications to retrieve, update, or delete user profiles or specific data elements.\n* `Data validation and security`: Implements validation rules to ensure data accuracy and adheres to security best practices for user data protection.\n\n#### Api Endpoints\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/auth-service-endpoints.png\" alt=\"endpoints\" \u003e\n\u003c/div\u003e\n\n## Service Registry\nA Service Registry acts as a centralized directory for all the individual services within the system. \nIt stores information about each service, including its:\n\n* `Name`: Unique identifier for the service.\n* `Location`: Hostname and port number where the service is running.\n* `Health status`: Whether the service is currently healthy and accepting requests.\n* `Metadata`: Additional information about the service, such as its capabilities and version.\n\n\u003cdiv align=\"center\"\u003e\n    \u003cimg src=\"res/auth-service-endpoints.png\" alt=\"endpoints\" \u003e\n\u003c/div\u003e\n\n### Built With\nThe microservices are built using below technologies\n1. `Languages`:  Java, Python, SQL, NoSQL\n\n\u003cdiv\u003e\n   \u003cimg src=\"res/java-logo.svg\" alt=\"Java\" width=\"40px\" style=\"margin-right: 20px;\"\u003e\n   \u003cimg src=\"res/python-logo.svg\" alt=\"Python\" width=\"33px\" style=\"margin-right: 20px;\"\u003e\n   \u003cimg src=\"res/sql-logo.svg\" alt=\"SQL\" width=\"40px\" style=\"margin-right: 20px;\"\u003e\n\u003c/div\u003e\n\n2. `Frameworks`: Spring Boot, Flask, Sklearn\n\u003cdiv\u003e\n   \u003cimg src=\"res/spring-logo.svg\" alt=\"spring boot\" width=\"40px\" style=\"margin-right: 20px;\"\u003e\n   \u003cimg src=\"res/flask-logo.svg\" alt=\"flask\" width=\"33px\" style=\"margin-right: 20px;\"\u003e\n\u003c/div\u003e\n\n3. `Database`:   MySQL, MongoDB\n\u003cdiv\u003e\n   \u003cimg src=\"res/mongo-logo.svg\" alt=\"mongodb\" width=\"33px\" style=\"margin-right: 20px;\"\u003e\n   \u003cimg src=\"res/mysql-logo.svg\" alt=\"mysql\" width=\"40px\" style=\"margin-right: 20px;\"\u003e\n\u003c/div\u003e\n\n4. `Tools`:      Docker, Postman, Anaconda\n\u003cdiv\u003e\n   \u003cimg src=\"res/docker-logo.svg\" alt=\"docker\" width=\"40px\" style=\"margin-right: 20px;\"\u003e\n   \u003cimg src=\"res/postman-logo.svg\" alt=\"postman\" width=\"33px\" style=\"margin-right: 20px;\"\u003e\n   \u003cimg src=\"res/anaconda-logo.svg\" alt=\"anaconda\" width=\"33px\" style=\"margin-right: 20px;\"\u003e\n\u003c/div\u003e\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#readme-top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n\u003c!-- GETTING STARTED --\u003e\n## Getting Started\n\n### Prerequisites\n\nYou should have the below software installed in your pc :\n* Python3\n* Java 21\n* Anaconda\n* Flask\n* XAMPP 8\n* MongoDB\n* and your preferred IDE or text editor\n\n\n### Installation\n\n1. Get a free API Key at [https://github.com/settings/tokens](https://github.com/settings/tokens)\n2. Clone the repo\n\n   ```sh\n   git clone https://github.com/kudzaiprichard/coin-compass.git\n   ```\n3. Open project in desired IDE or text editor\n\n\u003e For the predict service: flask, python\n\n1. Create a python environment\n    ```shell\n    python -m venv myenv\n    ```\n   \n2. Activate created environment\n    ```shell\n    source myenv/bin/activate\n    ```\n   \n3. Install required python packages\n    ```shell\n    pip install -r requirements.txt\n    ```\n   \n4. You can now run the system using below flask command\n    ```shell\n    flask run\n    ```\n\n\u003e For the other services, java, spring boot\n1. Open the services with IDE or Text editor\n2. Maven will load the project packages and project configurations\n\n\u003e NB: make sure your connected online\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#readme-top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n\u003c!--CONTRIBUTING--\u003e\n## Contributing\n\nIf you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag \"enhancement\".\nDon't forget to give the project a star! Thanks again!\n\n1. Fork the Project\n2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)\n3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)\n4. Push to the Branch (`git push origin feature/AmazingFeature`)\n5. Open a Pull Request\n\n### :fire: Contribution\n\nYour contributions are always welcome and appreciated. Following are the things you can do to contribute to this project.\n\n1. **Report a bug** \u003cbr\u003e\n   If you think you have encountered a bug, and I should know about it, feel free to report it [here]() and I will take care of it.\n\n2. **Request a feature** \u003cbr\u003e\n   You can also request for a feature [here](), and if it will viable, it will be picked for development.\n\n3. **Create a pull request** \u003cbr\u003e\n   It can't get better than this, your pull request will be appreciated by the community. You can get started by picking up any open issues from [here]() and make a pull request.\n\n\u003e If you are new to open-source, make sure to check read more about it [here](https://www.digitalocean.com/community/tutorial_series/an-introduction-to-open-source) and learn more about creating a pull request [here](https://www.digitalocean.com/community/tutorials/how-to-create-a-pull-request-on-github).\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#readme-top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n\u003c!-- LICENSE --\u003e\n## License\n\n\u003e Distributed under the MIT License. See `LICENSE.txt` for more information.\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#readme-top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n\n\n\n\u003c!-- CONTACT --\u003e\n## Contact\n\n\u003e Kudzai P Matizirofa - [linkedin.com/in/kudzai-prichard](https://linkedin.com/in/kudzai-prichard) - \u003ckudzaiprichard@gmail.com\u003e\n\nProject Link: [https://github.com/kudzaiprichard/coin-compass.git](https://github.com/kudzaiprichard/coin-compass.git)\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#readme-top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n\n\u003c!-- ACKNOWLEDGMENTS --\u003e\n## Acknowledgments\n\nlist of resources I found helpful and would like to give credit to.\n\n* [Choose an Open Source License](https://choosealicense.com)\n* [Spring boot documentation](https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/)\n* [Python3 documentation](https://docs.python.org/)\n* [Rest API with flask](https://pythonbasics.org/flask-rest-api/)\n* [Flask Documentation](https://flask.palletsprojects.com/)\n* [Linear Regression](https://www.ibm.com/topics/linear-regression#:~:text=Linear%20regression%20analysis%20is%20used,is%20called%20the%20independent%20variable.)\n* [GitHub Pages](https://pages.github.com)\n\n\u003cp align=\"right\"\u003e(\u003ca href=\"#readme-top\"\u003eback to top\u003c/a\u003e)\u003c/p\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkudzaiprichard%2Fcoin-compass","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkudzaiprichard%2Fcoin-compass","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkudzaiprichard%2Fcoin-compass/lists"}