Project Info
This project did not submit a demo video on Devpost.
Inspiration
The inspiration behind APIVerse stems from the common frustrations and time-consuming processes that developers and users alike face when integrating and utilizing APIs. Traditionally, users have to sift through extensive documentation to understand how to work with an API, figure out the required parameters, manage authentication tokens, and more. We wanted to create a platform that not only simplifies these steps but also leverages the power of Large Language Models (LLMs) to provide intuitive and conversational interactions with APIs.
What it does
APIVerse serves as a centralized platform that radically simplifies the API integration and utilization process. Users can effortlessly import APIs by uploading their documentation, while companies have the ability to publish and manage their APIs on the platform. With the assistance of LLMs, users can interact with APIs through natural language, asking for recommendations, and even sending requests verbally. Developers have the option to export configurations, making the platform versatile and adaptable to different needs. Essentially, APIVerse streamlines the entire API experience, making it more accessible, efficient, and user-friendly.
How we built it
APIVerse is built on a robust framework that integrates LLMs to interpret and process natural language inputs. The platform has a user-friendly interface for importing API documentation and managing API listings. On the backend, we developed algorithms to parse and interpret API documentation, extracting necessary information like endpoints, parameters, and authentication details. The LLMs are trained to understand API-related queries and provide accurate and helpful responses, recommendations, and assistance to the users.
Challenges we ran into
One of the major challenges was ensuring that the LLMs could accurately interpret and provide relevant information and recommendations based on varied and sometimes incomplete API documentation. Developing a system that could handle different documentation formats and standards required extensive testing and refinement. Additionally, ensuring a seamless and intuitive user experience while managing the complexities of API interactions posed significant design and development challenges.
Accomplishments we're proud of
We are incredibly proud of creating a platform that democratizes API interactions, making them accessible to a wider audience beyond just developers. APIVerse’s ability to provide conversational interactions with APIs, backed by the power of LLMs, represents a significant advancement in simplifying complex technical processes. The platform’s capacity to understand and process a variety of API documentation formats is another achievement that we are particularly proud of.
What we learned
Through the development of APIVerse, we gained valuable insights into natural language processing, machine learning, and the intricacies of API interactions. We learned about the challenges associated with interpreting diverse API documentation and the importance of a user-centric design to ensure an intuitive and efficient user experience.
What's next
The future of APIVerse is focused on continuous improvement and expansion. We plan to further enhance the LLMs’ capabilities, ensuring even more accurate and helpful interactions. We aim to expand the platform’s functionality to support more API types and documentation formats. Additionally, we are looking at integrating additional tools and resources to aid in API development and testing, creating a comprehensive ecosystem for API management and integration.
APIVerse (Cal Hacks 10.0)
🪐 APIVerse's goal is to provide a more convenient approach to utilizing APIs. We are in the process of developing an API platform that enables users to import API documentation from various sources and offers a natural conversational interface for interacting with the APIs.
💡: Make it simply to interact with technoloy!
Project Design
✨ Here is the high level design of the project architecture. (React + Flask)
Contribution
Author:
- Jingchao (Perry) Zhong
- Jiaxiang (Calvin) Li
- Junyi (Alex) Zhang
- Yufeng (Jimmy) Li
Analysis
View
Metric
- 33
- 11
- 1
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- FlaskIn code
- JavaScriptIn code
- LangChainIn code
- Next.jsIn code
- OpenAIIn code
- PythonIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
10 of 10 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
138 KB
Source files
71
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
liyufeng0802/APIVerse
100 files · 1.2 MB · @ 8ea4234
Structure
Interface
40 files · 40%Screens, components and styles rendered to the user.
Application logic
26 files · 26%Domain rules, services and shared utilities.
Data & schema
4 files · 4%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript76%
- Python17%
- CSS6%
- Markdown1%
- JavaScript0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
frontend/package.json
npm · 46- @chakra-ui/icons
- @chakra-ui/react
- @chakra-ui/system
- @chakra-ui/theme-tools
- @codemirror/legacy-modes
- @emotion/react
- @emotion/styled
- @heroicons/react
- @material-tailwind/react
- @tanstack/react-table
- @testing-library/jest-dom
- @testing-library/react
- @testing-library/user-event
- @uiw/codemirror-theme-tokyo-night
- @uiw/react-codemirror
- axios
- babel-cli
- babel-preset-es2015
- +28 more
requirements.txt
pypi · 6- flask
- flask-cors
- langchain
- numpy
- openai
- pyyaml
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.