UI design and For Detailed Development Requirements for AI API Project

UI design and For 1. Developer Requirements The company/development team must meet the following criteria to take on the project: • Technical Understanding and Qualifications: Full understanding of relevant development technologies and possession of company/professional development qualifications. • Project Experience: Proven track record of completing similar projects with successful outcomes. • Professional Team: A professional team with AI skills, with members who have extensive experience. • Good Communication Skills: Team members must have good communication skills to maintain smooth communication with the client and ensure the project progresses smoothly. • Long-term Cooperation Ability: This project is the first version, followed by the second and third versions for continuous development. After completing the project, the team must be able to provide continuous upgrades and functionality development support (expected cooperation period of at least two years). 2. Pre-development Preparation Before development, the company must provide a complete design plan with both text and images, including but not limited to: • UI Design Reference: Provide UI design reference examples to confirm page styles and user interaction experiences, reducing changes due to unclear design plans later on. • Functional Technical Logic: Determine the technical logic of the entire project to ensure the development direction meets the requirements. • Detailed Function Description: Describe all functional modules in detail, along with implementation details, clarifying development goals and technical solutions. 3. Payment Method • Contract Signing and Fund Escrow: After confirming the development plan is correct, both companies will sign a development contract, and we will pay the entire project fee into a third-party escrow platform. • Funds Release: The funds will be released only after the project is completed and accepted by us. Milestone-based payment is not accepted to avoid project interruptions if developers leave midway. 4. Source Code Security Check • Perform source code security checks on the open-source project, checking if the source code is encrypted or contains backdoors, malware, data theft, etc. • Conduct a thorough examination of the source code to ensure all ownership belongs to us. 5. Pre-development Capability Test • The development team is required to help solve simple technical problems such as logo modification bugs to verify their development capability. 6. Project Budget • The project budget is 200 USD. 7. Open-source Project Address • The open-source project to be used: [login to view URL] • Main Goal: Modify UI, fix bugs, add new functions, and optimize existing functions based on the open-source project. 8. Development Requirements 8.1 UI Design • Two Sets of UI Designs: Design 2 sets for the front-end and 1 set for the back-end, covering all pages including documents. • Complete Back-end Redesign: The current back-end UI is the same as the front￾end. It needs to be redesigned to differ from the front-end and provide more detailed function management. • No-code Module: Add a no-code UI editing module in the back-end to allow easy modification of the UI in the future. 8.2 Website Feature Expansion • Unlogged Homepage and Blog Module: Add a homepage for unlogged users and a Blog module for posting announcements and technical articles. • Multi-verification and Authorization Login: Support phone verification, Google authorized login, and WeChat authorized login. • Real-name Verification System: Support personal and enterprise real-name verification to ensure the authenticity of users' identities. 8.3 Subscription and Payment Modes • Individual User Packages: Support subscription on a monthly or annual basis. • Enterprise User Packages: Support credit recharge mode, with a minimum recharge amount of 10,000 RMB. • Custom Packages: Allow contracts with the team for specific functions and services. • Subscription contents and functional usage permissions for all packages must be configurable in the back-end. 8.4 Contract Generation Feature • Contract Generation Module: Users can generate purchase and cooperation contracts in the management panel to facilitate API calling agreements. 8.5 Payment Methods • Add support for payments via cryptocurrency, Stripe, and Airllex, to increase diversity in payment options. 8.6 API Call Logs • Detailed API Call Logs: Provide detailed data of users' API calls, including text, drawings, audio, video, voice, and document conversation records, with an option to download data in document format. Automatically download logs periodically and send them to the risk control system for content security checks. 8.7 Risk Control System • Automatic Call Detection: Detect whether APIs are being called multiple times, their specific usage locations, and check for malicious usage. • Prohibited Words Detection: Periodically retrieve call data and check whether API calls contain prohibited words, imposing usage restrictions on violating users. • IP Location Detection and Automatic Punishment Mechanism: Detect user call IP location and automatically execute punishment measures such as restricting user access based on rules. • Risk Control Data Visualization: Provide charts showing risk control situations, and support setting punishment levels and prohibited word lists. 8.8 Content Review System • Content Detection and Filtering: Automatically review the content of API calls in real-time, block prohibited and inappropriate content, ensuring compliant output. Third-party content review APIs can be used. 8.9 Administrator Permissions Assignment • Permissions Assignment System: Assign different permissions to employees to manage specific functional modules, ensuring flexibility in system management. 8.10 Customer Service Chat Function • Integrate third-party customer service chat APIs to provide online support to users. 8.11 Multi-language Support • Add a language switch button at the bottom of the page to support Chinese and English. 8.12 External API Integration Module • External API Integration Support: Support integration and distribution of other types of APIs, such as image editing APIs, search platform APIs, phone verification APIs, and email verification APIs, ensuring platform compatibility and extensibility. Assist in finding relevant platforms for API integration. 8.13 Account Security System • Two-level Protection Feature: Provide two-level protection to prevent account theft. • View and Delete Logged-in Devices: Ensure account security by allowing users to view and delete logged-in devices. 8.14 Chatbot Function • External Plugin Module: Support integration of external APIs (e.g., search engine APIs) for fine-tuning and support multimodal functionality to enhance chatbot interaction. 8.15 Invitation Feature • Users can share the platform, invite new users to register, and undergo real-name verification to receive corresponding credit rewards. If the invited user recharges, a proportional rebate is provided. 8.16 Comprehensive Back-end Management System • Back-end Management Features include: ◦ Employee Management and Permissions Assignment: Assign employee permissions to manage designated modules. ◦ Data Management and Settings: Configure website information (e.g., SEO, name, logo, title) and domain binding. ◦ User and Subscription Management: Manage users, subscriptions, and payments. ◦ API Management: Manage external APIs and AI model APIs. ◦ Dashboard and Risk Control Management: Manage dashboard and risk control system. ◦ No-code UI Editor Management: Enable future modifications of UI and features. ◦ Contract Generator Content Management, Language Switching Management, Account Security Management, Customer Chat Feature Management. ◦ User API Call Log and Real-name Verification Management. ◦ Chatbot Plugin Management, Blog Management, Login and Registration Management, Invitation Feature Management, etc. 9. Code Security and Function Guarantee • Code Security: Ensure all functionalities work properly and that there is no harmful content in the code. Code ownership must belong to us. • Prohibition of Licensed and Encrypted Source Code: No licensed or encrypted source code is allowed during development. • Bug Fixing: Any bugs must be fixed, ensuring all functions work properly at delivery, without trojans or security risks. 10. Secondary Development of Open-source Project • This project is based on secondary development of an open-source project. To facilitate future feature updates, ensure that custom functions and UI are maintained while allowing easy integration of the latest models or other updates from the original author. • Ensure the system has sufficient scalability based on the secondary development to add more functions in the future. Further consideration is needed for database design, modular development, and API extensibility to ensure the system can adapt to business changes and continue to evolve. • The development team must provide detailed code documentation and explanations after project completion to ensure no encrypted code or backdoors, verified by an independent third party. • A detailed maintenance and upgrade plan must be established to ensure the development team can continuously provide technical support in subsequent version updates and feature expansions, including periodic system checks, feature optimization, and urgent technical support, to ensure the long-term stability of the project.