API Integration Agent for Enterprise Billing Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current API vendor systems lack integration with enterprise systems, making it difficult to utilize and bill for API usage effectively, as they are not readily connected to facilitate functionalities like bill generation.

Innovation Solution

An API management system that integrates with enterprise systems such as CRM, ERP, and API consumption plan store, using an integration agent to coordinate communication, manage API products, and generate consumption documents based on usage data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If API vendor systems operate independently without integration, then system simplicity is maintained, but billing and usage tracking functionalities cannot be effectively implemented

Engineering Contradiction:
Improvebilling functionalityVSAvoidsystem integration
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

An integration agent is introduced as an intermediary component that bridges the API vendor system and enterprise systems. The integration agent receives API usage data from the API vendor system, processes it according to billing rules, and generates invoices through the enterprise system, enabling billing functionality without direct complex integration between the vendor and enterprise systems

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is divided into distinct functional modules: the API vendor system that handles API delivery, the integration agent that handles data transformation and coordination, and the enterprise system that handles billing operations. This segmentation allows each component to remain relatively simple while achieving complex billing functionality through their coordinated interaction

Inventive Principle:
Principle #1Segmentation

2Productivity

If enterprise systems are integrated with API vendor systems, then billing and usage tracking are enabled, but system complexity increases

Engineering Contradiction:
Improvebilling efficiencyVSAvoidsystem connection
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The integration agent is designed as a universal component that can interface with multiple different enterprise systems (ERP, CRM, accounting systems) through standardized protocols. This multi-functionality allows the same integration agent to enable billing across various enterprise systems without requiring custom integration logic for each system, thereby improving billing efficiency while controlling complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Measurement precision

If manual tracking of API usage is used, then implementation simplicity is maintained, but accuracy and automation of charge calculation suffer

Engineering Contradiction:
Improveusage tracking accuracyVSAvoidcharge calculation automation
Core Design Contradiction:
Measurement precisionVSExtent of automation

Solution Approach 1:

The system implements automated feedback loops where the integration agent continuously monitors API usage data, compares it against billing rules and subscription agreements, and automatically generates invoices. This automated feedback mechanism ensures precise tracking of usage and accurate charge calculation without manual intervention, while maintaining high levels of automation throughout the billing process

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9645862B2Computing consumption of application programming interfaces
Publication Date: 2017.05.09 SAP SE
  • US9645862B2 patent drawing
  • US9645862B2 patent drawing
  • US9645862B2 patent drawing

AI summary

Various embodiments of systems and methods for computing consumption of application programming interfaces (APIs) are described herein. Initially at an integration agent, a subscription request is received from an API management system for subscribing to an API product. Next at the integration agent, a consumption policy associated with the subscribed API product is determined, from a plurality of consumption policies received from the API management system, wherein the consumption policy includes a plurality of pre-defined policies mapped with a plurality of API consumption plans. Next at the integration agent, an API consumption plan associated with the determined consumption policy, from the plurality of API consumption plans stored in an API consumption plan store is identified. Finally at the integration agent, a consumption data for the subscribed plurality of API product is computed based on the identified API consumption plan.