An agent application full life cycle management method based on API interaction

Abstract

The application discloses an API interaction-based intelligent agent application full life cycle management method, and relates to the technical field of intelligent agent management. The method reads application credentials, running instances, interface permissions and field boundary data, and establishes a life cycle version; receives a business task request, associates the life cycle version, an interface strategy version, a source authorization version and a task valid deadline, and establishes a task record, an execution qualification connection record and a task reverse association record; verifies the task entry qualification, generates a temporary interface execution voucher bound with a task number before the task is exited, receives life cycle, credential state, interface strategy and source authorization changes, forms an invalid range record according to the task reverse association record and updates the execution qualification state; when an API request and an interface callback arrive, the temporary interface execution voucher, version data, the execution qualification connection record and the invalid range record are used to perform request forwarding, task blocking, callback restriction and external pending registration.

Description

Technical Field

[0001] This invention relates to the field of intelligent agent management technology, specifically to a method for managing the entire lifecycle of intelligent agent applications based on API interaction. Background Technology

[0002] Intelligent agent applications typically use API interfaces to call customer relationship management systems, office approval systems, work order systems, knowledge base systems, and other business systems to complete tasks such as information retrieval, task creation, data writing, process triggering, and result feedback. Existing management platforms generally have separate functions for intelligent agent registration, interface configuration, identity authentication, permission allocation, task scheduling, operation monitoring, and deregistration management. When a task is created, a calling task is generated based on the intelligent agent's identity, interface permissions, and business rules, and the calling task is written to the execution queue or retry queue.

[0003] In actual operation, after an agent is paused, deregistered, has its permissions revoked, its interface policy adjusted, its tool configuration updated, or its delegation relationship terminated, tasks already written to the execution queue, including pending tasks, delayed tasks, failed retry tasks, asynchronous callback tasks, and subtasks derived from that agent, may still carry historical access tokens, historical interface configurations, and historical task contexts to continue calling business APIs. In existing technologies, agent lifecycle states, permission policy states, task execution states, and API call credentials are typically maintained separately by different modules, lacking a mechanism for verifying and propagating the correlation of state changes. This means that even when the management platform has registered an agent as disabled, the corresponding business system may still receive and execute interface requests initiated by that agent, making it difficult to accurately identify the valid execution qualifications and calling basis of tasks in transit. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a method for managing the entire lifecycle of intelligent agent applications based on API interaction, thereby resolving the problems mentioned in the background section.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for full lifecycle management of intelligent agent applications based on API interaction, comprising: S1. Read the application certificate, running instance, interface permission information and interface field boundary information corresponding to the intelligent agent application, establish lifecycle record and generate lifecycle version; S2. Receive business task requests, associate lifecycle version, interface policy version, source authorization version and task validity deadline, and establish task records, execution qualification connection records and task reverse association records. S3. Verify the eligibility of the task record for joining the queue and write it into the task queue. Before the task leaves the queue, read the current lifecycle version, current interface policy version, current source authorization version and execution eligibility connection record, and generate a temporary interface execution certificate bound to the task number. S4. Receive changes in the intelligent agent application lifecycle, application certificate status, interface policy, and source authorization. Based on the task reverse association record, determine the associated tasks to be executed, retry tasks, tasks waiting for callback, and incomplete interface requests, form an invalidation range record, and update the execution qualification status of the corresponding tasks. S5. When the interface gateway receives API requests and interface callbacks, it reads the temporary interface execution credential, the current lifecycle version, the current interface policy version, the current source authorization version, the execution qualification connection record and the failure scope record, and performs API request forwarding, task blocking, callback restriction and external pending registration.

[0006] The present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the above-described method for full lifecycle management of intelligent agent applications based on API interaction is implemented.

[0007] Furthermore, in S1:

[0008] The lifecycle record is written to the intelligent agent application number, registration subject number, running instance number, application certificate number, running environment identifier, interface number list, interface policy version number set, and interface field boundary version number set;

[0009] When the application certificate is valid, the certificate binding instance is consistent, the registration subject is valid, the runtime environment is valid, the interface is enabled, and the field boundary status is valid, the lifecycle status is registered as the runtime status and a lifecycle version is generated.

[0010] Furthermore, the interface field boundary states are formed based on the interface request field list, the allowed read field list, the allowed write field list, and the prohibited outgoing field list;

[0011] If the request field list contains fields that are prohibited from being sent out, the field boundary status is registered as boundary invalid.

[0012] When there are unregistered fields in the requested field list, the field boundary status is registered as "boundary pending".

[0013] When the requested field list meets the field boundary information, the field boundary status is registered as boundary established.

[0014] Furthermore, in S2:

[0015] The execution qualification connection record is written with the task number, root task number, parent task number, agent application number, application certificate number, lifecycle version, interface number, interface policy version, interface field boundary version, request source number, source authorization version, business object number, request action category, and task validity deadline.

[0016] The task reverse association record associates the task number with the agent application number, application certificate number, lifecycle version, interface number, interface policy version, source authorization version, root task number, and parent task number.

[0017] Furthermore, in S3:

[0018] When the lifecycle status is running, the application certificate status is valid, the interface enable flag is enabled, the source authorization status is valid, the current time is earlier than the task's valid deadline, and the parent task's execution qualification status is valid, the task will be written into the waiting execution queue.

[0019] Before a task leaves the queue, a temporary interface execution credential bound to the task number is generated based on the current lifecycle version, the current interface policy version, the current source authorization version, and the execution qualification connection record.

[0020] Furthermore, in S4:

[0021] When the application lifecycle state of the intelligent agent changes to the paused state, the associated waiting tasks, retry tasks, waiting callback tasks and incomplete interface requests are located based on the task reverse association record to form an failure range record;

[0022] Update the execution eligibility status of tasks waiting to be executed and retry tasks to "eligibility suspended", update the callback eligibility status of tasks waiting for callbacks to "callback pending during suspension", and update the execution eligibility status of incomplete interface requests to "eligibility pending".

[0023] Furthermore, when the lifecycle state of an intelligent agent application changes to the deregistration pending cleanup state, the execution qualification status of tasks waiting to be executed and retry tasks is updated to qualification expired, the corresponding task status is updated to task terminated, and unused temporary interface execution credentials are updated to revoked; for tasks that have issued interface requests but have not received a final response, the revocation class interface information in the interface data is read and a revocation task record is established.

[0024] Furthermore, in S5:

[0025] When the interface gateway receives an API request, it compares the task number, agent application number, interface number, business object number, request action type, lifecycle version, interface policy version, and source authorization version in the temporary interface execution certificate with the current request information.

[0026] If the comparison is consistent, the credential status is valid, the execution qualification status is valid, and the invalidation range record does not match the current task, forward the API request.

[0027] Furthermore, when the interface gateway receives an interface callback, it reads the callback certificate number, list of allowed callback fields, lifecycle version, interface policy version, and source authorization version from the callback association record. When the callback time is later than the pause effective time, cancellation pending cleanup effective time, interface policy reduction effective time, or source authorization expiration effective time associated with the task, the task queue status is updated to external pending, and the callback fields are restricted from triggering the creation of derived tasks and downstream API requests.

[0028] Compared with existing technologies, this invention provides a method for managing the entire lifecycle of intelligent agent applications based on API interaction, which has the following beneficial effects: 1. By establishing lifecycle versions, execution qualification connection records, and task reverse association records, a correspondence is established between the lifecycle status, application certificate status, interface policy status, source authorization status of the intelligent agent application, and tasks in the task queue. When the intelligent agent application is paused, deregistered, its application certificate expires, its interface policy changes, or its source authorization changes, the task to be executed, retry tasks, tasks waiting for callbacks, and incomplete interface requests are determined based on the task reverse association records, and an expiration scope record is formed. At three nodes—task dequeueing, API request entering the interface gateway, and interface callback arrival—the current lifecycle version, current interface policy version, current source authorization version, execution qualification connection record, and expiration scope record are read for qualification verification, thereby preventing paused, deregistered, or authorized intelligent agent applications from continuing to use historical tasks, historical credentials, or late callbacks to drive business API calls. 2. Before a task leaves the queue, issue a temporary interface execution credential bound to the task number, and verify the consistency of the task number, agent application number, interface number, business object number, request action category, and version data before forwarding the interface request. For interface requests that have been issued but not completed after a status change, create a cancellation task according to the cancellation type interface data registered in the interface data, and restrict the triggering of derived task creation and downstream API requests for waiting callback tasks by limiting the callback field. This allows for the differentiation and handling of unexecuted tasks, in-transit tasks, and callback tasks while retaining traceability data such as external business serial numbers, interface response times, and basic callback statuses, thereby reducing abnormal business actions caused by inconsistencies in task status, permission status, and interface call status across business platform call chains. Attached Figure Description

[0029] Figure 1 This is a schematic diagram of the process of a method for managing the entire lifecycle of an intelligent agent application based on API interaction according to the present invention. Detailed Implementation

[0030] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0031] Example: Figure 1 A method for managing the entire lifecycle of intelligent agent applications based on API interaction is presented, including:

[0032] S1. Read the application certificate, running instance, interface permission information, and interface field boundary information corresponding to the intelligent agent application, establish a lifecycle record, and generate a lifecycle version. Specifically:

[0033] Before an intelligent agent application can be integrated into an enterprise business platform, it must submit registration information. This registration information consists of the intelligent agent application number, registration entity number, running instance number, application certificate number, operating environment identifier, deployment communication address, business type code, a list of proposed interface numbers, a list of proposed data categories, and a list of proposed business action categories.

[0034] The intelligent agent application ID is assigned by the enterprise business platform after the intelligent agent application access application is approved. It is used to distinguish intelligent agent applications with different business purposes, such as customer consultation, work order processing, approval workflow, procurement application, financial verification, and knowledge query. The registration entity ID comes from the department ID, project ID, legal entity ID, or authorized business account ID in the enterprise's unified identity directory. The runtime instance ID comes from the instance registration information written when the intelligent agent application starts up. It is used to distinguish the execution entities of the same intelligent agent application in different controlled operating environments.

[0035] The application certificate number is derived from the certificate issuance and registration data, which stores the certificate binding instance number, issuing entity number, certificate effective date, certificate expiration date, certificate status, and certificate revocation date. The runtime environment identifier comes from the controlled environment directory maintained by the enterprise business platform. This directory registers the environment number, allowed communication address range, allowed certificate types, environment review date, and environment validity flag. The list of proposed API call numbers comes from the API directory. Each API number in the directory corresponds to an API address, request method, request field list, response field list, API enable flag, API policy version number, business action category, and API call boundary information.

[0036] The list of data categories to be processed and the list of business action categories to be executed shall be filled in by the registered entity based on the actual business scope of the intelligent agent application. The data categories shall adopt the pre-registered data category codes such as customer information, order information, work order information, approval information, procurement information, financial verification information, knowledge document information, and attachment information. The business action categories shall adopt the pre-registered action category codes such as query, write, trigger, callback registration, and cancellation.

[0037] Upon receiving the registration materials, the system first reads the certificate issuance registration information corresponding to the application certificate number and verifies the identity information for the application certificate number, runtime instance number, registration entity number, and current time. If the application certificate number does not exist in the certificate issuance registration information, the application registration status of the intelligent agent is written to the pending registration status, and the reason for the certificate not existing is recorded. If the certificate binding instance number and runtime instance number are inconsistent, the application registration status of the intelligent agent is written to the pending registration status, and the reason for the instance inconsistency is recorded. If there is no registered attribution relationship between the issuing entity number and the registration entity number, the application registration status of the intelligent agent is written to the pending registration status, and the reason for the entity inconsistency is recorded. If the current time is earlier than the certificate effective time, later than the certificate expiration time, or the certificate status is revoked, the application registration status of the intelligent agent is written to the pending registration status, and the reason for the certificate time mismatch or the reason for certificate revocation is recorded.

[0038] After the application certificate number, runtime instance number, registration entity number, and current time all meet the identity verification requirements, the controlled environment directory corresponding to the runtime environment identifier is read to verify the runtime environment information, including the deployment communication address, allowed communication address range, certificate type, environment review date, and environment validity marker. If the deployment communication address does not fall within the allowed communication address range, the registration status remains pending registration; if the certificate type is not a permitted certificate type for the current runtime environment, the registration status remains pending registration; if the environment validity marker is expired, the registration status remains pending registration; if the environment review date exceeds the review validity period registered in the controlled environment directory, the registration status remains pending registration.

[0039] The validity period of the operational environment verification is jointly registered by the operational environment security inspection record, instance communication test record, and enterprise online acceptance record. In this implementation, the validity period of the verification for internal controlled operational environments is registered as 90 days, and the validity period of the verification for external controlled operational environments is registered as 30 days. This time boundary is used to identify whether the operational environment registration data needs to be re-verified, and is not a fixed duration for different enterprise deployment environments.

[0040] After identity verification and runtime environment verification are passed, the system reads the interface directory, interface permission information, and interface field boundary information corresponding to the list of interface numbers to be called. The interface permission information registers the interface number, allowed registration entity number, allowed business type code, allowed data category list, allowed action category list, interface enable flag, and interface policy version number. The interface field boundary information registers the interface number, allowed read field list, allowed write field list, allowed callback field list, prohibited outbound field list, and interface field boundary version number.

[0041] For each interface number to be called, verify whether the interface enable flag is enabled, whether the registration entity number is within the allowed registration entity number range, whether the business type code is within the allowed business type code range, whether all data categories to be processed are within the allowed data category list, and whether all business action categories to be executed are within the allowed action category list.

[0042] If the request field list corresponding to the interface number to be called contains a field that is prohibited from being sent out, writing the interface field boundary status to the boundary will not be valid; if the request field list contains a field name that is not registered in the interface field boundary information, the interface field boundary status will be written as "boundary pending"; if the entire request field list falls within the corresponding range of the allowed read field list and allowed write field list, and no field is prohibited from being sent out, writing the interface field boundary status to the boundary will be valid.

[0043] The field names in the interface field boundary information are derived from the business interface release information and interface integration records. The field type, maximum length, whether nullables are allowed, and whether callbacks are allowed are all registered according to the interface release information. If the interface information, interface permission information, or interface field boundary information is missing, the intelligent agent application registration status remains in the pending registration state, and the registration information will not enter the activation process.

[0044] After the above verification is passed, a lifecycle record is generated. The lifecycle record contains the agent application ID, registration entity ID, runtime instance ID, application certificate ID, runtime environment identifier, interface ID list, interface policy version number set, interface field boundary version number set, registration time, and lifecycle status. Upon initial registration verification, the lifecycle status is set to "Pending Activation." After the administrator account submits the activation action, the application certificate ID, runtime environment identifier, interface policy version number set, and interface field boundary version number set are reread and compared with the corresponding data saved when the "Pending Activation" status was generated.

[0045] When all data remains unchanged, the lifecycle status is updated to running status, and a lifecycle version is generated. The lifecycle version uses the same agent application ID as the counting object. When it first enters the running status, it is registered as version 1. A new lifecycle version is generated when the running status changes to paused status, paused status is restored to running status, running status changes to deregistration pending cleanup status, deregistration pending cleanup status changes to deregistered status, application certificate is replaced, running instance is replaced, interface permission scope is reduced, or interface permission scope is expanded.

[0046] Each lifecycle version contains the lifecycle status, effective time, source of status change, application certificate number, running instance number, set of interface policy version numbers, and set of interface field boundary version numbers. The source of status changes comes from the corresponding change serial number in administrator account operation records, certificate status change records, runtime environment review records, and interface permission change records. When the lifecycle status is pending registration, pending activation, paused, pending deregistration, or deregistered, the intelligent agent application will not be used as the target intelligent agent application in subsequent business task requests; when the lifecycle status is running, the business task creation process in step S2 is initiated.

[0047] S2. Receive business task requests, associate lifecycle versions, interface policy versions, source authorization versions, and task expiration dates, and establish task records, execution qualification connection records, and task reverse association records, specifically:

[0048] The system receives business task requests, which consist of a business request number, a request source number, a business type code, a target intelligent agent application number, a target interface number, a business object number, a set of request fields, a request action category, a task validity deadline, a callback requirement flag, and a parent task number. The business request number originates from the request sequence number initiated by the business personnel terminal, the business system interface, or the authorized intelligent agent application.

[0049] The request source ID is used to identify the business personnel account, business system account, and parent intelligent agent application ID. The business object ID uses the corresponding business primary key from customer ID, order ID, work order ID, approval form ID, purchase application ID, payment verification ID, document ID, and knowledge item ID. The request field set is organized according to the request field list corresponding to the target interface ID, and the field name, field type, and field length are consistent with the interface field boundary information.

[0050] The request action category is checked against the business action category corresponding to the target interface number. The effective deadline for the task comes from the business processing time limit registered in the business process information. When business personnel have adjustment authority, they can fill in a new effective deadline for the task within the maximum processing time limit registered in the business process information. The callback request flag is formed based on the interface information of the target interface number. When the interface information registers an interface that needs to return processing results asynchronously, the callback request flag is set to "callback required"; when the interface information registers an interface that returns the final processing result synchronously, the callback request flag is set to "no callback required". The parent task number is used to associate the parent task of derived tasks. For tasks submitted directly by business personnel terminals and business system interfaces, the parent task number is null.

[0051] After a business task request enters the processing flow, it reads the current lifecycle version corresponding to the target intelligent agent application number, the current interface policy version corresponding to the target interface number, the current source authorization version corresponding to the request source number, the source authorization boundary information corresponding to the business object number, the task's effective deadline, and the interface field boundary information. The source authorization version comes from the source authorization information, which registers the request source number, authorization version number, allowed business object scope, allowed action category, authorization effective time, authorization deadline, authorization status, and authorization change serial number.

[0052] If the business object number is not within the allowed business object range, no task record will be created for the current business task request; if the requested action category is not within the allowed action categories, no task record will be created for the current business task request; if the current time is earlier than the authorization effective time, later than the authorization expiration time, or the authorization status is invalid, no task record will be created for the current business task request; if the request field set contains prohibited outgoing fields, unregistered fields, or fields with mismatched types, the current business task request will be written to the task pending status.

[0053] When the target agent application's current lifecycle state is not running, the current business task request writes the agent's "not running" state. When the interface enable flag corresponding to the target interface number is not enabled, the current business task request writes the interface "unavailable" state. All of the above states are written to the business request processing record, which stores the business request number, target agent application number, target interface number, business object number, processing time, and state reason code.

[0054] When the target intelligent agent application is currently in the running state, the target interface is enabled, the request source authorization status is valid, the business object number is within the allowed business object range, the request action category is within the allowed action categories, and the request field set conforms to the interface field boundary information, a task record is created. The task record contains the task number, business request number, target intelligent agent application number, running instance number, target interface number, business object number, request source number, request action category, task creation time, task effective deadline, callback requirement flag, parent task number, queue status, and task status.

[0055] The task number consists of the business date, business type code, target agent application number, and sequence number. The queue status is initially set to "pending enqueue," and the task status is initially set to "task valid." After a task record is established, an execution qualification link record is formed according to the task number. The execution qualification link record stores the identity basis, interface basis, source authorization basis, field boundary basis, parent task basis, and time boundary basis that the current task possessed at the time of creation.

[0056] The execution qualification connection record contains the task number, root task number, parent task number, agent application number, running instance number, application certificate number, lifecycle version, interface number, interface policy version, interface field boundary version, request source number, source authorization version, business object number, request action category, task effective deadline, callback requirement flag, callback address version, allowed request count, allowed retries count, current request count, current retries count, and execution qualification status. In directly created business tasks, the root task number is the same as the task number, and the parent task number is null. In derived tasks triggered by a parent task, the root task number inherits from the root task record, and the parent task number is written with the parent task number.

[0057] The allowed number of requests and allowed number of retries are derived from the interface call boundary data. This data is comprised of the call instructions published by the interface provider, interface integration records, historical exception work order records, and business acceptance records. In this implementation, query interfaces are registered with 3 allowed requests and 2 allowed retries; write interfaces are registered with 1 allowed request and 0 allowed retries; trigger interfaces are registered with 1 allowed request and 0 allowed retries; callback registration interfaces are registered with 1 allowed request and 1 allowed retries; and cancellation interfaces are registered with 2 allowed requests and 1 allowed retries.

[0058] The current request count and current retries count are both registered as 0 when the task is created. The execution eligibility status is registered as valid when the task is created. The callback address version comes from the callback address data, which registers the business platform number, callback address, callback certificate number, list of allowed callback fields, callback enable flag, callback address version, and callback address effective time. When the callback requirement is marked as no callback required, the callback address version is registered as an empty value; when the callback requirement is marked as required, the callback address version must be the currently enabled callback address version. If the callback address data is missing, the callback enable flag is not enabled, or the callback certificate number is missing, the task status is set to "task pending".

[0059] After the execution qualification association record is established, a task reverse association record is established. The task reverse association record uses the agent application number, application certificate number, lifecycle version, interface number, interface policy version, request source number, source authorization version, parent task number, root task number, and callback address version as association fields, and writes the task number, queue position number, retry reservation number, callback association number, and current execution qualification status.

[0060] The queue position number, retry reservation number, and callback association number in the task reverse association record are registered as null values ​​when the task is created, and the corresponding numbers are added when enqueuing, retrying, and registering callbacks. When the root task needs to generate a derived task, the preceding action category, subsequent action category, subsequent intelligent agent application number, subsequent interface number, allowed start conditions, and abort conditions are read from the business process data.

[0061] If the fields in the pre-action completion record meet the allowed start conditions, the current root task status is "task valid," and the current parent task's execution eligibility status is "eligible," then a derived task is created. The derived task's execution eligibility link record is written with the parent task number, root task number, parent task eligibility number, and delegation chain number. The root task's delegation chain number is registered as 1, and the derived task's delegation chain number is incremented by 1 from the parent task's delegation chain number.

[0062] In this implementation, the maximum value of the delegation chain number for a single root task is registered as 4. This boundary is derived from business process analysis data, historical abnormal task tracing records, and business launch acceptance records. When the delegation chain number reaches 4, the task record is written to the manual review status, and no new derived tasks are created. The task record, execution qualification link record, and task reverse association record formed in step S2 enter the queuing qualification verification process in step S3.

[0063] S3. Verify the enqueue eligibility of the task record and write it to the task queue. Before the task is dequeued, read the current lifecycle version, current interface policy version, current source authorization version, and execution eligibility connection record to generate a temporary interface execution credential bound to the task number. Specifically:

[0064] Read the task record in the pending queue state, execution qualification connection record, task reverse association record, current lifecycle version, current interface policy version, current source authorization version, current interface field boundary version, current callback address version, and current task validity deadline, and perform queue qualification verification. In the current lifecycle version, the lifecycle status is running, the application certificate status is valid, the interface enable flag corresponding to the current interface policy version is enabled, the authorization status corresponding to the current source authorization version is valid, the current time has not reached the task validity deadline, the request field set is consistent with the field boundary data corresponding to the current interface field boundary version, the callback requirement is marked as needed, the callback enable flag corresponding to the callback address version is enabled, and the parent task execution qualification status is valid when the parent task number is not null. When all the above conditions are met, update the queue status of the task record to the waiting execution state, and write the task number, task validity deadline, task priority, and current execution qualification status to the task queue.

[0065] Task priority is derived from the business time limit level in the business process documentation, which is divided into immediate processing, same-day processing, normal processing, and low-priority processing. The earliest dequeue time for immediate processing is the enqueue time; the earliest dequeue time for same-day processing is 5 minutes after the enqueue time; the earliest dequeue time for normal processing is 15 minutes after the enqueue time; and the earliest dequeue time for low-priority processing is 30 minutes after the enqueue time. These earliest dequeue times are jointly recorded based on the queue service processing capacity, average response time during interface integration, business process time limits, and online trial operation records. After writing the queue position number into the task queue, this number is then added to the task's reverse association record.

[0066] When the lifecycle status in the current lifecycle version is paused, the execution eligibility status of the task record is updated to paused, and the queue status is updated to blocked. When the lifecycle status is deregistration pending cleanup or deregistered, the execution eligibility status of the task record is updated to invalid, and the queue status is updated to canceled. When the application certificate status is revoked or the certificate expiration time has arrived, the execution eligibility status of the task record is updated to invalid, and the queue status is updated to blocked. When the interface enable flag is disabled, the execution eligibility status of the task record is updated to invalid, and the queue status is updated to blocked. When the source authorization status is invalid, the execution eligibility status of the task record is updated to invalid, and the queue status is updated to blocked. When the task's effective expiration time has arrived, the task status is updated to invalid, and the queue status is updated to canceled. When the request field set is inconsistent with the current interface field boundary version, the execution eligibility status is updated to pending verification, and the queue status is updated to manual review. When the parent task's execution eligibility status is paused, invalid, pending verification, or terminated, the derived task's execution eligibility status is updated to invalid, and the queue status is updated to blocked.

[0067] All types of entry qualification verification and processing are written into the task qualification processing record. The task qualification processing record includes the task number, processing time, lifecycle version read, interface policy version read, source authorization version read, execution qualification status, queue status, and processing reason code.

[0068] After a task reaches its earliest dequeue time, the task number, queue position number, and current execution eligibility status are read from the task queue. Then, the current lifecycle version, current API policy version, current source authorization version, current API field boundary version, execution eligibility link record, and task reverse association record are read again. If the current lifecycle version, current API policy version, and current source authorization version match the lifecycle version, API policy version, and source authorization version in the execution eligibility link record, the application certificate status, task expiration time, current request count, allowed request count, parent task execution eligibility status, and root task execution eligibility status are read.

[0069] When the application certificate is valid, the current time has not reached the task's valid deadline, the current number of requests is less than the allowed number of requests, the parent task's execution qualification status is valid, and the root task's execution qualification status is valid, a temporary interface execution credential application record bound to the task number is generated.

[0070] The temporary interface execution credential application record contains the task number, root task number, agent application number, running instance number, application certificate number, current lifecycle version, current interface policy version, current source authorization version, interface number, business object number, request action category, request field boundary version, allowed number of requests, current number of requests, task validity deadline, and credential application time.

[0071] Temporary interface execution credentials are issued individually based on the task number and are not pre-issued when the task enters the queue. The temporary interface execution credential contains the task number, root task number, agent application number, interface number, business object number, request action type, current lifecycle version, current interface policy version, current source authorization version, credential validity period, credential expiration time, and number of available uses.

[0072] The validity period for credentials is registered as 120 seconds for query interfaces, 60 seconds for write interfaces, 60 seconds for trigger interfaces, 120 seconds for callback registration interfaces, and 90 seconds for revocation interfaces. The validity period is registered based on interface gateway verification records, interface response records, internal enterprise communication records, and external business interface integration records.

[0073] The available number of requests matches the remaining number of requests allowed for the current task. After the temporary interface execution credential is issued, the queue status of the task record is updated to "dequeued," the current request count is incremented by 1, the interface request time is written to the task record, and the credential number is written to the execution qualification link record and the task reverse association record. If any of the current lifecycle version, current interface policy version, or current source authorization version is inconsistent with the corresponding version saved in the execution qualification link record, a temporary interface execution credential is not generated, the execution qualification status of the task record is updated to "qualification pending verification," and the queue status is updated to "blocked."

[0074] When the application certificate status, interface policy information, source authorization information, and execution qualification connection record are unreadable, the execution qualification status of the task record is updated to "qualification pending verification," and the queue status is updated to "blocked." The temporary interface execution credential, queue position number, and task qualification handling record generated in step S3 provide a basis for locating in-transit tasks and canceling unused credentials when processing status changes in step S4.

[0075] S4. Receive changes to the intelligent agent application lifecycle, application certificate status, interface policy, and source authorization; determine the associated pending tasks, retry tasks, callback-waiting tasks, and incomplete interface requests based on the task reverse association record; form an invalidation range record and update the execution eligibility status of the corresponding tasks, specifically:

[0076] It receives status change events resulting from changes in the intelligent agent application lifecycle, application certificate status, interface policy, and source authorization. Each status change event contains the change serial number, changed object type, changed object number, previous status, new status, previous version, new version, change effective time, change source number, change reason code, list of affected interface numbers, list of affected action categories, list of affected data categories, scope of affected business objects, and cleanup deadline. The changed object type uses the intelligent agent application, running instance, application certificate, business interface, interface policy, source authorization, callback address, and corresponding type in the runtime environment.

[0077] The change source number comes from the corresponding serial number in the administrator account operation log, certificate management log, interface management log, business authorization management log, and runtime environment verification log. The change reason code adopts the corresponding reason from the following: business deactivation, temporary suspension, cancellation application, certificate expiration, certificate revocation, instance replacement, interface offline, field boundary reduction, action category reduction, data category reduction, authorization revocation, business object scope reduction, callback address deactivation, and runtime environment verification failure.

[0078] When the status of a change event in the intelligent agent application lifecycle is paused, the task number, queue position number, retry appointment number, callback association number, and credential number, which are equal to the current changed object number, are read from the task reverse association record to form an failure scope record. The failure scope record contains the change serial number, changed object number, affected task number, affected queue position number, affected retry appointment number, affected callback association number, affected credential number, change effective time, failure scope status, and cleanup deadline.

[0079] For affected tasks in the "Pending Execution" or "Delayed Execution" states, the execution eligibility status will be updated to "Eligibility Suspended" and the queue status to "Blocked." For affected tasks in the "Retry" state, the next dequeue time corresponding to the retry appointment number will be canceled, the execution eligibility status will be updated to "Eligibility Suspended," and the queue status will be updated to "Blocked." For affected tasks in the "Pending Callback" state, the external business serial number, interface request time, and callback address version will be retained, and the callback eligibility status will be updated to "Callback Pending Review During Suspension." For affected tasks that have been dequeued but have not received an interface response, the execution eligibility status will be updated to "Eligibility Pending Review," and the "Request Sent, Suspended, Pending Review" status will be written. In the "Suspended" state, no new temporary interface execution credentials will be issued, no new derived tasks will be created, and downstream tasks will not be automatically triggered based on the callback field.

[0080] When a change event in the lifecycle of an intelligent agent application results in a status of "cancellation pending cleanup," all related tasks are processed according to the scope of failure. For affected tasks in the "waiting to execute" or "delayed execution" status, the execution eligibility status is updated to "eligibility invalidated," the task status is updated to "task terminated," and the queue status is updated to "cancelled." For affected tasks in the "retry" status, the retry reservation record is cancelled, the execution eligibility status is updated to "eligibility invalidated," the task status is updated to "task terminated," and the queue status is updated to "cancelled." For affected tasks in the "waiting for callback" status, the callback eligibility status is updated to "callback pending verification after cancellation," and the queue status is updated to "external pending verification." For affected tasks that have been dequeued and have not received an interface response, the interface data corresponding to the current interface number is read. When the interface data registers a cancellation-type interface, a cancellation task record is created.

[0081] The task cancellation record includes the original task number, root task number, original interface number, external business serial number, cancellation / change serial number, cancellation reason code, and cancellation-type interface number. Cancelled tasks enter a separate dequeue qualification verification process, requiring a new temporary interface execution credential bound to the cancelled task number; the original task's temporary interface execution credential is not reused. When the cancellation-type interface returns "cancelled," the original task queue status is updated to "cancelled"; when the cancellation-type interface returns "completed," "cancellation not supported," or "no cancellation interface provided," the original task queue status is updated to "externally pending verification."

[0082] Temporary interface execution vouchers that have not yet expired and have not been used will have their voucher status updated to "Revoked," with the revocation time written into the voucher status data. Callback association records will have their callback status updated to "Restricted After Cancellation," accepting only basic callback fields such as external business serial number, interface response status, and interface response time; action fields used to create derived tasks and downstream interface fields will not be accepted. After all affected tasks, vouchers, and callback association records have been processed, their lifecycle status will be updated from "Cancelled Pending Cleanup" to "Cancelled."

[0083] In an interface policy change event, the system reads the interface number, list of changed fields, list of changed action categories, list of changed data categories, change effective time, and historical task processing flags. Based on the task reverse association record, it locates the interface number, interface policy version, and the task associated with the current change object. When a field from the changed field list appears in the task request field set, the execution eligibility status is updated to "eligibility invalidated"; when the task request action category is within the changed action category list, the execution eligibility status is updated to "eligibility invalidated"; when the task processing data category is within the changed data category list, the execution eligibility status is updated to "eligibility invalidated"; and when the historical task processing flag indicates that further execution is not allowed, the execution eligibility status is updated to "eligibility invalidated". For tasks that are not yet dequeued and are in an invalidated state, the queue status is updated to "blocked"; for tasks that have already issued interface requests, the queue status is updated to "external pending verification"; and for tasks waiting for callbacks, the callback eligibility status is updated to "callback pending verification after interface policy change".

[0084] In the event of source authorization change, read the request source number, source authorization version, scope of affected business objects, category of affected action, authorization status and change effective time, and locate the task associated with the request source number, source authorization version, business object number and request action category based on the task reverse association record.

[0085] When the business object number is within the scope of affected business objects and the request action category is within the affected action category, the execution eligibility status of tasks not yet dequeued is updated to "eligibility invalidated," and the queue status is updated to "blocked." Retry tasks have their retry appointments cancelled. The callback eligibility status of tasks waiting for callbacks is updated to "callback pending verification after source authorization withdrawal." Tasks that have already issued interface requests are written to the "response pending verification after source authorization withdrawal" status. The invalidation scope record, execution eligibility status, callback eligibility status, and credential status updated in step S4 serve as the real-time verification basis for receiving API requests and interface callbacks in step S5.

[0086] S5. When the interface gateway receives API requests and interface callbacks, it reads the temporary interface execution credential, current lifecycle version, current interface policy version, current source authorization version, execution qualification connection record, and invalidation scope record, and performs API request forwarding, task blocking, callback restriction, and external pending registration. Specifically:

[0087] When an interface request reaches the interface gateway, the system reads the task number, root task number, agent application number, running instance number, application certificate number, interface number, business object number, request action category, lifecycle version, interface policy version, source authorization version, temporary interface execution credential number, and request field set from the interface request. For the current task number, the system reads the execution qualification connection record, current lifecycle version, current interface policy version, current source authorization version, current interface field boundary version, current invalidation scope record, temporary interface execution credential status, and task record.

[0088] The temporary interface execution credential status data stores the credential number, bound task number, bound agent application number, bound interface number, bound business object number, bound request action type, bound lifecycle version, bound interface policy version, bound source authorization version, credential effective time, credential expiration time, available times, and credential status. Before an interface request enters the forwarding process, the system verifies whether the bound task number matches the task number in the interface request, whether the bound agent application number matches the agent application number in the interface request, whether the bound interface number matches the interface number in the interface request, whether the bound business object number matches the business object number in the interface request, whether the bound request action category matches the request action category in the interface request, whether the bound lifecycle version, bound interface policy version, and bound source authorization version match the current corresponding version, whether the credential status is valid, whether the current time is between the credential effective time and the credential expiration time, whether the available count is greater than zero, whether the execution qualification status in the execution qualification connection record is valid, whether there are any unprocessed invalid records associated with the current task number, root task number, agent application number, interface number, and source authorization version in the invalidation scope record, and whether the request field set conforms to the list of allowed read fields, the list of allowed write fields, and the list of prohibited outgoing fields corresponding to the current interface field boundary version.

[0089] When a temporary interface execution credential does not exist, the interface request writes a credential non-existent status; when the credential status is revoked, the interface request writes a revoked status; when the current time is earlier than the credential effective time or later than the credential expiration time, the interface request writes a credential time mismatch status; when the available number of times is zero, the interface request writes a credential time exhaustion status; when any of the following fields—task number, agent application number, interface number, business object number, request action category, lifecycle version, interface policy version, or source authorization version—is inconsistent, the interface request writes a request binding inconsistency status; when the execution qualification status is qualification suspended, qualification expired, qualification pending verification, or qualification terminated, the interface request writes a task qualification invalid status; when there are unprocessed failure records in the failure scope record, the interface request writes a failure scope hit status; when the request field set contains prohibited outgoing fields, unregistered fields, or fields with mismatched types, the interface request writes a field boundary mismatch status.

[0090] When the above states occur, the interface gateway will not forward the current API request and will update the queue status of the task record to "Blocked" or "Manual Review". When the execution qualification status is "Qualification Suspended" or "Qualification Expired", the queue status will be updated to "Blocked"; when the execution qualification status is "Qualification Pending Review" or "Field Boundary Mismatch", the queue status will be updated to "Manual Review". The interface request processing record will contain the task number, interface number, credential number, request time, current lifecycle version, current interface policy version, current source authorization version, execution qualification status, processing status, and status reason code.

[0091] After the binding field, version field, credential status, execution qualification status, invalidation range record, and field boundary information are all verified, the interface gateway will reduce the number of available temporary interface execution credentials by 1, update the current request count in the task record to the current request count plus 1, write the interface request time into the task record, and forward the API request to the business interface corresponding to the target interface number.

[0092] Both write-type and trigger-type interfaces read the idempotency flag data from the interface documentation during forwarding. The idempotency flag data registers the idempotency flag field name, the idempotency flag validity period, and duplicate request handling rules. The interface gateway combines the task number and the interface number and writes them into the idempotency flag field. The target business interface uses this field to identify whether the same task has been accepted. After the interface response returns the corresponding response status (accepted, completed, failed, request format mismatch, interface permission denied, interface temporarily unavailable, or waiting for callback), the interface gateway generates an interface response record.

[0093] The interface response record contains the interface response number, task number, interface number, response time, response status, response field set, external business serial number, and idempotency flag. When the response status is "processing complete," the record reads the interface request time, interface response time, current lifecycle version effective time, current interface policy version effective time, current source authorized version effective time and expiration scope.

[0094] If no record of the current task's failure range is found between the interface request time and the interface response time, and the response field set matches the interface field boundary version in the task execution qualification connection record, the task status is updated to "Task Completed," the queue status is updated to "Completed," and the execution qualification status is updated to "Qualification Terminated." If the interface response time is later than the pause effective time, cancellation pending cleanup effective time, interface policy reduction effective time, or source authorization expiration effective time, the task queue status is updated to "External Pending Review," the execution qualification status is updated to "Qualification Pending Review," and it is prohibited to create derived tasks based on the current response field set.

[0095] When the interface response status is "Waiting for Callback," a callback association record is created. This record contains the task number, root task number, interface number, external business serial number, callback address version, callback certificate number, list of allowed callback fields, callback start time, callback end time, lifecycle version, interface policy version, source authorization version, and callback eligibility status. The callback end time is derived from the maximum callback waiting time registered in the interface documentation.

[0096] In this implementation, the maximum callback waiting time is registered as 10 minutes for the Customer Relationship Management (CRM) interface, 30 minutes for the Office Approval interface, 15 minutes for the Work Order Creation interface, and 60 minutes for the Financial Verification interface. These durations are based on the business interface release materials, interface integration records, historical work order processing time records, and business process time limits. If the callback deadline arrives but no callback is received, the callback eligibility status is updated to "Callback Timeout Pending Review," the task queue status is updated to "External Pending Review," and no retry task is created.

[0097] When the interface gateway receives an interface callback, it reads the task number, root task number, interface number, external business serial number, callback certificate number, callback field set, and callback time from the callback request. It also reads the callback association record, current lifecycle version, current interface policy version, current source authorized version, current invalidation scope record, and execution qualification connection record. If the callback certificate number matches the callback certificate number in the callback association record, the callback field set does not exceed the allowed callback field list, the callback time does not exceed the callback deadline, the current invalidation scope record does not contain any unprocessed invalidation records associated with the current task, and the current lifecycle version, current interface policy version, and current source authorized version match the corresponding versions stored in the callback association record, then the gateway receives the callback field set and updates the interface response record based on the callback field set.

[0098] When the callback certificate number is inconsistent, the callback request is written to the callback certificate mismatch status; when the callback field set exceeds the allowed callback field list, the excess fields are not written to the business task information, and the callback eligibility status is updated to callback field out of bounds; when the callback time exceeds the callback deadline, the callback eligibility status is updated to late callback pending review; when there are unprocessed failure records associated with tasks in the current failure range record, the callback eligibility status is updated to callback affected by status change, only the external business serial number, callback time, and basic response status are retained; when the current lifecycle version, current interface policy version, current source authorization version, and the corresponding version in the callback associated record are inconsistent, the callback eligibility status is updated to callback version inconsistency, and the task queue status is updated to external pending review.

[0099] When the callback eligibility status is pending (paused), pending after cancellation, pending after interface policy change, pending after source authorization withdrawal, callback affected by status change, callback version inconsistent, or late callback pending), the callback field set is not used to automatically create derived tasks or automatically trigger downstream interface requests. Each API request, interface response, callback processing, task blocking, credential revocation, and external pending processing is written to the audit association record. The audit association record stores the task number, root task number, agent application number, application certificate number, lifecycle version, interface number, interface policy version, source authorization version, credential number, status change serial number, interface request time, interface response time, callback time, execution eligibility status, queue status, and processing time.

[0100] The customer service agent application ID is AG-CS-014, the running instance ID is INS-CS-014-A, the application certificate ID is CERT-CS-014-2026, the current lifecycle version is 7, and the lifecycle status is running. The refund application creation interface corresponding to this agent application has the ID CRM-RF-001, the current interface policy version is 12, and the source authorization version is 5.

[0101] At 10:15:03 on June 22, 2026, business personnel account U-702 submitted a refund request. The business request number was REQ-20260622-0185, the order number was ORD-20260618-467, the refund amount was 1580 yuan, the request action type was write, and the task's effective deadline was 18:00 on the same day. The platform created a task number TASK-20260622-CS-0421 and wrote the execution qualification connection record, in which the lifecycle version was 7, the interface policy version was 12, the source authorization version was 5, the allowed number of requests was 1, and the allowed number of retries was 0.

[0102] At 10:15:10 on June 22, 2026, the task passed the team departure qualification verification and issued a temporary interface execution credential bound to TASK-20260622-CS-0421. The credential is valid for 60 seconds and can be used once. After verifying that the task number, interface number, business object number, lifecycle version, interface policy version, and source authorization version are consistent, the interface gateway sends a refund application creation request to the customer relationship management platform. At 10:15:12, the customer relationship management platform returned an accepted status and returned the external business serial number CRM-RF-93421, and the task entered the waiting callback state.

[0103] At 10:16:12 on June 22, 2026, due to an abnormal running instance certificate, the administrator account changed the lifecycle status of AG-CS-014 from running to paused, generating lifecycle version 8. The platform located TASK-20260622-CS-0421 based on the task's reverse association record, updated the callback eligibility status of this task to "callback pending during pause," and updated the subsequent action restriction mark to "prohibit automatic derivation."

[0104] At 10:17:05 on June 22, 2026, a refund request callback was created on the Customer Relationship Management platform, carrying the refund request number RF-20260622-733. The interface gateway compared the callback time with the pause effective time, confirming that the callback time was later than the pause effective time. It then updated the task queue status to "External Pending Review" and the execution eligibility status to "Eligibility Pending Review," saving only the external business transaction number, refund request number, callback time, and basic response status. It did not create any derived tasks for the approval agent application based on this callback result.

[0105] The work order intelligent agent application number is AG-WO-011, and the corresponding on-site maintenance work order creation interface number is WO-CR-008. The interface business action category is write. At 8:45 on June 22, 2026, the platform created task number TASK-20260622-WO-0068. The task request field set includes the device serial number field, fault description field, and maintenance location field. The corresponding interface policy version at the time of task creation is 16. The task enters the delayed execution queue, and the earliest departure time is 9:00.

[0106] At 8:52:30 AM on June 22, 2026, the interface administrator updated the interface policy version of WO-CR-008 from 16 to 17 and removed the device serial number field from the list of fields allowed to be written. Based on the task reverse association record, the platform located the task to be executed with interface number WO-CR-008 and interface policy version 16. It identified that the request field set of TASK-20260622-WO-0068 contained the device serial number field, updated the execution eligibility status of the task to "eligibility invalid," and updated the queue status to "blocked."

[0107] At 9:00 AM on June 22, 2026, the message queue service submitted a dequeue request for TASK-20260622-WO-0068. The platform reads the current interface policy version 17, the interface policy version 16 when the task was created, and the interface policy change record, confirms that the device serial number field is an affected field, does not generate a temporary interface execution certificate, and does not send an interface request to WO-CR-008.

[0108] The aforementioned agent application ID, runtime instance ID, application certificate ID, interface ID, task ID, lifecycle version, interface policy version, source authorization version, queue status, interface response status, and callback status are derived from agent application registration data, runtime instance registration data, certificate issuance data, interface directory data, task queue records, interface gateway request logs, business platform response logs, and callback logs, respectively. The allowed request count, allowed retries count, temporary interface execution credential validity period, earliest dequeue time, callback waiting time, and maximum delegation chain sequence number are registered based on interface provider release data, interface integration records, business process time limits, historical exception work order records, online trial operation records, and business acceptance records, and are updated with the interface policy version, lifecycle version, or business process version. They are not considered fixed parameters across interfaces, business platforms, or operating environments.

[0109] This embodiment also provides a computer-readable storage medium storing a computer program. When the computer program is loaded and executed by the processor corresponding to the enterprise business platform, scheduling control terminal, or interface gateway, it reads the application certificate information, running instance information, interface permission information, and interface field boundary information of the intelligent agent application, and establishes a lifecycle record and lifecycle version; receives business task requests and establishes task records, execution qualification connection records, and task reverse association records; verifies the queuing qualification of tasks, and generates a temporary interface execution credential bound to the task number before the task leaves the queue; responds to changes in the intelligent agent application lifecycle, application certificate status, interface policy, and source authorization, forms an invalidation scope record, and updates the task execution qualification status; when receiving API requests and interface callbacks, it performs request forwarding, task blocking, callback restriction, and external pending verification registration based on the temporary interface execution credential, current version information, execution qualification connection record, and invalidation scope record.

[0110] The above content is only a specific embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for managing the entire lifecycle of intelligent agent applications based on API interaction, characterized in that, include: S1. Read the application certificate, running instance, interface permission information and interface field boundary information corresponding to the intelligent agent application, establish lifecycle record and generate lifecycle version; S2. Receive business task requests, associate lifecycle version, interface policy version, source authorization version and task validity deadline, and establish task records, execution qualification connection records and task reverse association records. S3. Verify the eligibility of the task record for joining the queue and write it into the task queue. Before the task leaves the queue, read the current lifecycle version, current interface policy version, current source authorization version and execution eligibility connection record, and generate a temporary interface execution certificate bound to the task number. S4. Receive changes in the intelligent agent application lifecycle, application certificate status, interface policy, and source authorization. Based on the task reverse association record, determine the associated tasks to be executed, retry tasks, tasks waiting for callback, and incomplete interface requests, form an invalidation range record, and update the execution qualification status of the corresponding tasks. S5. When the interface gateway receives API requests and interface callbacks, it reads the temporary interface execution credential, the current lifecycle version, the current interface policy version, the current source authorization version, the execution qualification connection record and the failure scope record, and performs API request forwarding, task blocking, callback restriction and external pending registration.

2. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 1, characterized in that, In S1: The lifecycle record is written to the intelligent agent application number, registration subject number, running instance number, application certificate number, running environment identifier, interface number list, interface policy version number set, and interface field boundary version number set; When the application certificate is valid, the certificate binding instance is consistent, the registration subject is valid, the runtime environment is valid, the interface is enabled, and the field boundary status is valid, the lifecycle status is registered as the runtime status and a lifecycle version is generated.

3. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 2, characterized in that, The boundary states of interface fields are formed based on the list of interface request fields, the list of fields allowed to be read, the list of fields allowed to be written, and the list of fields prohibited from being sent out. If the request field list contains fields that are prohibited from being sent out, the field boundary status is registered as boundary invalid. When there are unregistered fields in the requested field list, the field boundary status is registered as "boundary pending". When the requested field list meets the field boundary information, the field boundary status is registered as boundary established.

4. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 1, characterized in that, In S2: The execution qualification connection record is written with the task number, root task number, parent task number, agent application number, application certificate number, lifecycle version, interface number, interface policy version, interface field boundary version, request source number, source authorization version, business object number, request action category, and task validity deadline. The task reverse association record associates the task number with the agent application number, application certificate number, lifecycle version, interface number, interface policy version, source authorization version, root task number, and parent task number.

5. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 1, characterized in that, In S3: When the lifecycle status is running, the application certificate status is valid, the interface enable flag is enabled, the source authorization status is valid, the current time is earlier than the task's valid deadline, and the parent task's execution qualification status is valid, the task will be written into the waiting execution queue. Before a task leaves the queue, a temporary interface execution credential bound to the task number is generated based on the current lifecycle version, the current interface policy version, the current source authorization version, and the execution qualification connection record.

6. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 1, characterized in that, In S4: When the application lifecycle state of the intelligent agent changes to the paused state, the associated waiting tasks, retry tasks, waiting callback tasks and incomplete interface requests are located based on the task reverse association record to form an failure range record; Update the execution eligibility status of tasks waiting to be executed and retry tasks to "eligibility suspended", update the callback eligibility status of tasks waiting for callbacks to "callback pending during suspension", and update the execution eligibility status of incomplete interface requests to "eligibility pending".

7. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 6, characterized in that, When the lifecycle state of an intelligent agent application changes to the deregistration pending cleanup state, the execution qualification status of tasks waiting to be executed and retry tasks is updated to qualification expired, the corresponding task status is updated to task terminated, and unused temporary interface execution credentials are updated to revoked; for tasks that have issued interface requests but have not received a final response, the revocation class interface information in the interface data is read and a revocation task record is established.

8. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 1, characterized in that, In S5: When the interface gateway receives an API request, it compares the task number, agent application number, interface number, business object number, request action type, lifecycle version, interface policy version, and source authorization version in the temporary interface execution certificate with the current request information. If the comparison is consistent, the credential status is valid, the execution qualification status is valid, and the invalidation range record does not match the current task, forward the API request.

9. The method for full lifecycle management of intelligent agent applications based on API interaction according to claim 8, characterized in that, When the interface gateway receives an interface callback, it reads the callback certificate number, list of allowed callback fields, lifecycle version, interface policy version, and source authorization version from the callback association record. If the callback time is later than the pause effective time, cancellation pending cleanup effective time, interface policy reduction effective time, or source authorization expiration effective time associated with the task, the task queue status is updated to external pending, and the callback fields are restricted from triggering the creation of derived tasks and downstream API requests.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the API-based intelligent agent application lifecycle management method as described in claim 1.

Images