Intent-Based API Routing with Ontology Clustering and Code Synthesis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing API systems lack an efficient method for intent-based routing and integration, leading to suboptimal utilization and user experience in accessing multiple APIs for specific tasks.
Innovation Solution
A system and method for intent-based API integration that utilizes an API schema ingestion module, ontology building, and hierarchical clustering to route intent-based requests to the most relevant APIs, synthesizing integration code for seamless API interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional API access methods are used, then developers can access multiple APIs, but the complexity of integrating and routing requests to multiple APIs increases significantly
Solution Approach 1:
The patent introduces an intermediary system that sits between the user and multiple APIs, translating user intents into appropriate API calls. This mediator handles the complexity of routing, parameter mapping, and integration logic, allowing users to access multiple APIs through simple intent-based requests without dealing with the underlying integration complexity
Solution Approach 2:
The patent creates a universal intent-based interface that can handle multiple different APIs through a single standardized method. This universal layer performs multiple functions including request routing, parameter translation, response aggregation, and error handling, eliminating the need for separate integration code for each API
2Reliability
If developers manually integrate each API, then specific API functionality is achieved, but the time and effort required for integration increases
Solution Approach 1:
The patent performs preliminary actions by pre-defining intent schemas, parameter mappings, and routing rules before actual API integration is needed. The system pre-processes and structures the integration logic in advance, so when a user makes an intent-based request, the integration is already prepared and can be executed immediately without manual configuration
Solution Approach 2:
The patent creates reusable templates and schemas that capture the essential structure of API integrations. These templates can be copied and adapted for similar integration scenarios, eliminating the need to manually integrate each API from scratch and significantly reducing integration time while maintaining reliability
3Adaptability or versatility
If multiple APIs are accessed for a single task, then functionality and options increase, but the difficulty of determining which API to use increases
Solution Approach 1:
The patent implements feedback mechanisms where the system analyzes user intents, compares them against known API capabilities, and provides intelligent routing decisions. The system learns from usage patterns and API performance feedback to improve its ability to match intents with appropriate APIs, reducing the difficulty of API selection over time
Solution Approach 2:
The intermediary system acts as a smart router that translates high-level user intents into specific API selections. It handles the complexity of evaluating multiple API options by implementing automated matching logic that considers intent parameters, API capabilities, and contextual factors, making the selection process transparent and effortless for users
Data Source
Figure 1
Figure 2
Figure 2A
AI summary
A service platform for routing intent-based API requests to the most relevant APIs, comprising: a data ingestion subsystem, configured to retrieve API schema definitions and context information from external sources and store them in an API schema library; an ontology mining subsystem, configured to identify ontologies for said stored APIs, cluster the identified ontologies hierarchically and label said hierarchies with meaningful labels; an evaluation subsystem, configured to evaluate a set of APIs based on chosen datasets and metrics or by externally provided quality signals; an API dispatcher subsystem, configured to receive an intent-based request and identify the API schema and API Endpoint that match the request; and an API integration subsystem, configured to receive said intent-based request and said matched API schema and API Endpoint and synthesize an integration code.