Business execution method and device based on intelligent agent, medium and equipment

Abstract

The embodiment of the invention discloses an agent-based service execution method, which comprises the following steps that: an agent management system receives a state query call request sent by an agent when the agent is used by a first user, queries a subscription state of the first user, and returns the subscription state to the agent; receiving a subscription calling request returned by the agent when the agent determines that the first user does not have the use right, querying each subscription plan associated with the agent, sending the subscription plans to the first user, and when a payment request sent by the first user to a target subscription plan is received, sending the target subscription plan to the agent; and payment is carried out on the target subscription plan by adopting a payment account of the first user, and the subscription state of the first user is updated. Through the method, the intelligent agent does not need to have a function of maintaining the subscription state of each user, and does not need to have a function of providing payment service for the user who needs to subscribe to the intelligent agent, so that the workload required by an intelligent agent developer for developing the intelligent agent can be effectively reduced, and the development efficiency is improved.

Description

Technical Field

[0001] This specification relates to the field of computer technology, and in particular to a business execution method, apparatus, medium and device based on intelligent agents. Background Technology

[0002] With the development of artificial intelligence (AI) technology, large language models (LLM) have been widely applied in various fields.

[0003] An intelligent agent is an intelligent system that combines an LLM (Limited Language Management) with business code for executing business operations. The intelligent agent can leverage the reasoning capabilities of an LLM to break down user-inputted instructions in natural language into several steps, and for each step, use the corresponding business code to execute that step, ultimately performing the corresponding business for the user.

[0004] How to make it easier for agents to develop and improve the efficiency of agents development is an urgent problem to be solved. Summary of the Invention

[0005] This specification provides an agent-based business execution method, apparatus, storage medium, and electronic device to partially solve the problems existing in the prior art.

[0006] The embodiments in this specification adopt the following technical solutions: This specification provides a business execution method based on an intelligent agent, which is applied to an intelligent agent management system. The method includes: Receive a status query request sent by the intelligent agent; the status query request is sent by the intelligent agent when the first user uses the intelligent agent; Based on the user identifier of the first user carried in the status query call request, query the subscription status of the first user to the agent; Return the subscription status to the agent; Receive the subscription invocation request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent; In response to the subscription call request, query the pre-configured subscription plans associated with the agent and send each subscription plan to the first user; When a payment request is received from the first user for a target subscription plan among the subscription plans, the payment for the target subscription plan is made using the payment account corresponding to the first user's user identifier, and the first user's subscription status for the agent is updated.

[0007] This specification provides a business execution device based on an intelligent agent, which is applied to an intelligent agent management system. The device includes: The status query module is used to receive a status query call request sent by the agent; the status query call request is sent by the agent when the first user uses the agent; according to the user identifier of the first user carried in the status query call request, the module queries the subscription status of the first user to the agent; and returns the subscription status to the agent. The subscription module is configured to receive a subscription invocation request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent; in response to the subscription invocation request, query the pre-configured subscription plans associated with the agent, and send each subscription plan to the first user; The payment module is used to make payment for the target subscription plan using the payment account corresponding to the user identifier of the first user when it receives a payment request sent by the first user for the target subscription plan among the subscription plans, and to update the first user's subscription status for the agent.

[0008] This specification provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned agent-based business execution method.

[0009] This specification provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the above-described agent-based business execution method.

[0010] This specification provides a computer program product, which includes a computer program that, when executed by a processor, implements the aforementioned agent-based business execution method.

[0011] The above-described at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: This specification discloses a business execution method based on an intelligent agent. The intelligent agent management system receives a status query request sent by the intelligent agent when it is used by a first user, queries the first user's subscription status to the intelligent agent, and returns the subscription status to the intelligent agent. It also receives a subscription request returned by the intelligent agent when it determines, based on the subscription status, that the first user does not have usage rights. The system queries pre-configured subscription plans associated with the intelligent agent and sends them to the first user. When a payment request for a target subscription plan is received from the first user, the system uses the first user's payment account to make payment for the target subscription plan and updates the first user's subscription status to the intelligent agent. Through this method, the intelligent agent itself does not need to maintain the subscription status of each user, nor does it need to provide payment services to users who need to subscribe to the intelligent agent. This effectively reduces the workload required for intelligent agent developers and improves development efficiency. Attached Figure Description

[0012] The accompanying drawings, which are included to provide a further understanding of this specification and form part of this specification, illustrate exemplary embodiments and are used to explain this specification, but do not constitute an undue limitation thereof. In the drawings: Figure 1 This specification provides a schematic diagram of a business execution method based on an intelligent agent, as illustrated in an embodiment. Figure 2 A schematic diagram of a business execution device based on an intelligent agent provided in the embodiments of this specification; Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this specification. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this specification.

[0014] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0015] Figure 1 This specification provides a schematic diagram of a business execution method based on an intelligent agent, which specifically includes: S100: Receives status query call requests sent by the intelligent agent.

[0016] In the embodiments described in this specification, the following are employed: Figure 1 The method shown can be based on an agent performing business operations, and can be an agent management system.

[0017] Generally, when developing an agent, developers need to create not only the business logic code for executing business processes, but also code for managing user subscriptions and collecting payments. This is because users typically need to pay the agent developer to use the agent; this is what this specification refers to as user "subscription." An agent often has multiple subscription rules, such as per-use or per-time subscriptions, and the amounts required for different rules vary. Having to develop both the business logic code and the code for managing user subscriptions reduces the development efficiency of the agent.

[0018] Therefore, this specification introduces an agent management system in its embodiments. This system provides agent developers with all the necessary LLMs for developing agents, allowing them to directly develop agents on the system. The system also allows developers to deploy their developed agents directly. The system can then leverage its user base to drive traffic to deployed agents, enabling more users to utilize them. Furthermore, the system provides a status query interface for checking user subscription status and a subscription interface for allowing users to subscribe to the agent. Agents can directly query user subscription status via the status query interface and subscribe via the subscription interface, eliminating the need for developers to write code within the agent, thus improving development efficiency.

[0019] Of course, agent developers may choose not to use the agent management system to develop agents, nor may they deploy the developed agents on the agent management system. As long as the developed agents can communicate with the agent management system and can call the status query interface, subscription interface and other interfaces opened by the agent management system, they can also be managed through the agent management system.

[0020] The device used to host the intelligent agent management system can be a server or a server cluster consisting of multiple servers. This device is located in the background. Both intelligent agent developers and users of intelligent agents can log in to the intelligent agent management system using their own login accounts to develop or use intelligent agents.

[0021] For ease of description, the user who uses the services provided by the agent will be referred to as the first user, and the agent developer will be referred to as the second user. The example given is that the second user directly develops and deploys the agent on the agent management system.

[0022] After the second user deploys the developed agent on the agent management system, the first user can log in to the agent management system using their own login account and use the agent deployed on the agent management system. Thus, when the agent is used by the first user, it can send a status query call request through the Model Context Protocol (MCP) to call the status query interface opened by the agent management system.

[0023] Specifically, the intelligent agent can include the login account of the first user, i.e. the user identifier of the first user, in the status query call request, and encapsulate the status query call request using MCP before sending it to the intelligent agent management system. The user identifier of the first user carried in the status query call request is the input parameter of the status query interface.

[0024] S101: Based on the user identifier of the first user carried in the status query call request, query the subscription status of the first user to the intelligent agent.

[0025] In the embodiments described in this specification, the agent management system maintains the subscription status of all first users to all agents deployed on the agent management system. When the agent management system receives a status query request carrying the user identifier of the first user sent by the aforementioned agent based on MCP, it can query the subscription status of the first user to the agent through the status query interface according to the user identifier carried in the status query request.

[0026] The subscription status of the first user to an agent described in this specification includes at least two subscription statuses: subscribed and unsubscribed. It may also include subscription details, which will be explained in detail later.

[0027] S102: Return the subscription status to the agent.

[0028] After the agent management system queries the first user's subscription status to the agent, it can return the subscription status to the agent.

[0029] If the subscription status is "subscribed", the agent can determine that the first user has permission to use the agent after receiving the subscription status, and the agent can then provide business services to the first user.

[0030] S103: Receive the subscription call request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent.

[0031] If the subscription status is unsubscribed, the agent can determine that the first user does not have permission to use the agent after receiving the subscription status. At this time, the agent can send a subscription call request to the agent management system to invoke the subscription interface based on MCP.

[0032] Specifically, the agent can include the user identifier of the first user in the subscription request, encapsulate the subscription request using MCP, and then send it to the agent management system. The user identifier of the first user carried in the subscription request is the input parameter of the subscription interface.

[0033] S104: In response to the subscription call request, query the pre-configured subscription plans associated with the agent and send each subscription plan to the first user.

[0034] In response to a subscription call request sent by an agent, the agent management system can first query the subscription plans that the second user has pre-configured for the agent in the agent management system, i.e., the subscription plans managed by the agent, through the subscription interface, and then send the subscription plans to the first user according to the user identifier of the first user carried in the subscription call request.

[0035] The subscription plan in the embodiments of this specification includes at least subscription rules and an amount to be paid. The subscription rules are the charging rules for the first user when using the agent, and the amount to be paid is the amount the first user needs to pay to the second user under these charging rules. For example, assuming a subscription plan associated with the agent is "30 yuan for 100 uses," then if the first user uses this subscription plan, the agent's charging rule is per use, the number of uses is 100, and the amount to be paid is 30 yuan.

[0036] After the intelligent agent management system sends the subscription plans associated with the aforementioned intelligent agents to the first user, the first user can select the desired subscription plan from the various subscription plans associated with the intelligent agent as the target subscription plan according to the subscription rules and the amount to be paid. The user can also include the subscription plan identifier of the target subscription plan in the payment request and then send the payment request to the intelligent agent management system.

[0037] S105: When a payment request is received from the first user for a target subscription plan among the subscription plans, the payment for the target subscription plan is made using the payment account corresponding to the user identifier of the first user, and the subscription status of the first user for the agent is updated.

[0038] In the embodiments of this specification, the intelligent agent management system can call the payment function of the payment system through the payment interface. Specifically, when the intelligent agent management system receives a payment request sent by the first user, it can pass the amount to be paid in the target subscription plan corresponding to the subscription plan identifier carried in the payment request, the user identifier of the first user, and the receiving account of the second user pre-configured on the intelligent agent management system as input parameters to the payment interface to call the payment system.

[0039] The payment system can then query the payment account corresponding to the user's identifier based on the user's identifier.

[0040] It should be noted that the user identifier of the first user mentioned in this specification is not the same concept as the payment account of the first user. The user identifier is the login account used by the first user to log in to the intelligent agent management system and / or the payment system, while the payment account is the account bound to the user identifier of the first user for payment purposes, and the payment account contains funds. The user identifier used by the first user to log in to the intelligent agent management system and the user identifier used to log in to the payment system may be the same or different. If they are different, the payment system can first query the user identifier used to log in to the payment system that is pre-bound to the user identifier used by the first user to log in to the intelligent agent management system, and then query the payment account corresponding to the user identifier used to log in to the payment system. For ease of description, the following explanation will only use the example where the user identifier used by the first user to log in to the intelligent agent management system and the user identifier used to log in to the payment system are the same user identifier.

[0041] After the payment system locates the first user's payment account, it can create a payment order containing the payment account, the amount to be paid in the target subscription plan, and the second user's receiving account. At this point, the payment order contains the necessary triplets for payment: the payment account, the amount to be paid, and the receiving account.

[0042] Then, the payment system can return an authorization query message to the first user based on the first user's user identifier, inquiring whether the first user authorizes the payment system to allow the use of the first user's payment account to pay the amount to be paid to the second user. When the payment system receives the authorization confirmation message returned by the first user, it can use the payment account to process the payment settlement for the payment order created above.

[0043] As can be seen from the above payment process, for the sake of payment security, the first user's payment account never passes through the first user during the entire process. The purpose of the authorization inquiry message sent by the payment system to the first user is to ask the first user whether he / she authorizes the payment system to use the first user's payment account to pay for the payment order. The payment account is not transferred between the two.

[0044] Once the payment system successfully pays the aforementioned payment order using the first user's payment account, it can return the successful payment result to the intelligent agent management system. The intelligent agent management system can then update the first user's subscription status to the intelligent agent, that is, update the subscription status from unsubscribed to subscribed, and send the updated subscription status to the aforementioned intelligent agent, so that the intelligent agent can confirm that the first user now has the permission to use the intelligent agent, thereby providing business services to the first user.

[0045] Of course, the above description is based on the example that the intelligent agent management system and the payment system are two separate systems. The intelligent agent management system and the payment system can also be the same system or be carried by the same device. This specification does not impose any restrictions on this.

[0046] Using the above method, the agent itself does not need to have the function of maintaining the subscription status of each user, nor does it need to have the function of providing payment services for users who need to subscribe to the agent. It only needs to call the corresponding function interface opened in the agent management system, which can effectively reduce the workload required for agent developers to develop the agent and improve development efficiency.

[0047] Furthermore, the second user can pre-configure their own payment account and the various subscription plans associated with the agent in the agent management system.

[0048] Specifically, when configuring a payment account, the second user can send a payment account configuration request corresponding to that smart agent to the smart agent management system. This request can include the smart agent identifier and the second user's payment account or user identifier. The second user can first register as a payment user (e.g., a merchant user) in the aforementioned payment system. After registration, the payment system will assign a payment account to the second user. The second user can then bind this payment account to their user identifier. When sending the payment account configuration request, the second user can include both the smart agent identifier and their own user identifier in the request. Alternatively, the second user can obtain their own payment account information from the payment system. In this case, when sending the payment account configuration request, the second user can include both the smart agent identifier and the obtained payment account information in the request.

[0049] The intelligent agent management system can determine the intelligent agent corresponding to the intelligent agent identifier carried in the received payment account configuration request, and save the second user's payment account carried in the payment account configuration request, thus establishing the association between the intelligent agent corresponding to the intelligent agent identifier and the second user's payment account. Alternatively, based on the second user's user identifier carried in the payment account configuration request, it can query the payment account bound to the second user's user identifier from the payment system, save the queried payment account, and establish the association between the intelligent agent corresponding to the intelligent agent identifier and the queried payment account.

[0050] When configuring the various subscription plans for the agent, the second user can send a subscription plan configuration request corresponding to the agent to the agent management system. This request carries the agent's identifier. Upon receiving the subscription plan configuration request, the agent management system can return a subscription plan configuration page containing various preset subscription plan templates to the second user. These subscription plan templates are pre-saved in the agent management system and can include per-use and time-based subscription plan templates. The per-use template can be formatted as "? money used ? times", while the time-based template can be formatted as "? money used ? time". The "?" can be manually set by the second user.

[0051] After receiving and viewing the subscription plan configuration page sent by the agent management system, the second user can select a target subscription plan template from the preset templates and configure it to obtain a subscription plan. The second user can set multiple subscription plans through the subscription plan configuration page and then return all the set subscription plans to the agent management system through the same page. Alternatively, the user can set a subscription plan and then return it to the agent management system after each plan is set. The agent management system then obtains and stores at least one subscription plan set by the second user, and establishes an association between each obtained subscription plan and the agent based on the agent identifier carried in the subscription plan configuration request.

[0052] In addition, the intelligent agent management system can set a unique subscription plan identifier for each subscription plan configured by the second user, and bind the subscription plan identifier to the user identifier of the first user after the first user pays for the target subscription plan.

[0053] After the agent management system configures the subscription plans associated with the agent, Figure 1 In step S105, if the subscription rule in the target subscription plan selected by the first user is a subscription rule that includes available counts, then after the first user pays for the target subscription plan in step S105, the agent management system can update the first user's subscription status to the agent to "subscribed" and add the available counts included in the target subscription plan to the first user's current available counts for the agent. The updated current available counts will be used as the subscription details in the updated subscription status of the first user for the agent.

[0054] If the subscription rule in the target subscription plan selected by the first user includes the available time, then after the first user pays for the target subscription plan in step S105, the intelligent agent management system can update the first user's subscription status to the intelligent agent to "subscribed". Based on the current time and the available time included in the target subscription plan, the system determines the latest time when the first user has the right to use the intelligent agent, and then uses the latest time as the subscription details in the updated subscription status of the first user to the intelligent agent.

[0055] Correspondingly, in Figure 1In step S102, if the first user's subscription status to the agent is "subscribed," the agent, upon receiving this subscription status, can determine that the first user has the permission to use the agent. At this point, the agent can provide business services to the first user. After providing business services to the first user, the agent can also send a subscription status update request to the agent management system based on MCP. This subscription status update request is used to call the subscription status update interface opened by the agent management system. The subscription status update request can carry the user identifier of the first user using the agent, and can also carry the number of times the agent has provided services to the first user, as input parameters to the subscription status update interface. Upon receiving the subscription status update request, the agent management system, in response to the request, can update the first user's subscription status to the agent through the subscription status update interface, based on the first user's user identifier carried in the subscription status update request.

[0056] Specifically, the intelligent agent management system can first query the subscription plan identifier bound to the user identifier of the first user, and determine the target subscription plan subscribed to by the first user based on the queried subscription plan identifier. Then, based on the target subscription plan subscribed to by the first user, it can determine whether the subscription rules contained in the target subscription plan include subscription rules that include available counts. If so, based on the number of services provided by the intelligent agent to the first user carried in the subscription status update call request, the number of available counts (subscription details) contained in the first user's subscription status is subtracted from the number carried in the subscription status update call request. If the number of available counts contained in the first user's subscription status is not greater than 0 after subtracting the number carried in the subscription status update call request, the first user's subscription status is updated to unsubscribed; otherwise, the first user's subscription status remains subscribed. If the subscription rules contained in the target subscription plan subscribed to by the first user do not include subscription rules that include available counts, the first user's subscription status can be updated to unsubscribed at a time no earlier than the latest time contained in the first user's subscription status; otherwise, the first user's subscription status remains subscribed. Of course, if the subscription rules in the target subscription plan subscribed to by the first user do not include the available number of subscriptions, the intelligent agent management system also needs to update the first user's subscription status in real time or automatically according to a set period using the above method, which will not be elaborated here.

[0057] The above is an example of a business execution method based on an intelligent agent provided in this specification. Based on the same idea, this specification also provides corresponding devices, storage media, and electronic devices.

[0058] Figure 2This specification provides a schematic diagram of a business execution device based on an intelligent agent, which is applied to an intelligent agent management system. The device includes: The status query module 200 is used to receive a status query call request sent by the intelligent agent; the status query call request is sent by the intelligent agent when the first user uses the intelligent agent; according to the user identifier of the first user carried in the status query call request, the module queries the subscription status of the first user to the intelligent agent; and returns the subscription status to the intelligent agent. The subscription module 201 is configured to receive a subscription invocation request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent; in response to the subscription invocation request, query each pre-configured subscription plan associated with the agent, and send each subscription plan to the first user; The payment module 202 is used to make payment for the target subscription plan using the payment account corresponding to the user identifier of the first user when it receives a payment request sent by the first user for the target subscription plan among the subscription plans, and to update the first user's subscription status for the smart agent.

[0059] Optionally, the device further includes: The configuration module 203 is configured to receive a payment account configuration request sent by the second user corresponding to the smart agent before the payment module 202 makes payment for the target subscription plan using the payment account corresponding to the user identifier of the first user; save the payment account of the second user carried in the payment account configuration request; and establish an association relationship between the smart agent and the payment account. The payment module 202 is specifically used to create a payment order based on the payment account corresponding to the user identifier of the first user, the amount to be paid contained in the target subscription plan, and the receiving account associated with the smart agent; and to make payment for the payment order using the payment account.

[0060] Optionally, the device further includes: The configuration module 203 is used to receive a subscription plan configuration request sent by the second user corresponding to the intelligent agent; in response to the subscription plan configuration request, return a subscription plan configuration page containing various preset subscription plan templates to the second user; obtain and store at least one subscription plan configured by the second user through the subscription plan configuration page, and establish an association relationship between the obtained subscription plans and the intelligent agent.

[0061] Optionally, the subscription plan includes at least the subscription rules and the amount to be paid; The payment module 202 is specifically used to: when the subscription rule includes available counts, add the available counts included in the target subscription plan to the first user's current available counts for the agent, and use the updated current available counts as the updated subscription status of the first user for the agent; when the subscription rule includes available duration, determine the latest time when the first user has the right to use the agent based on the current time and the available duration included in the target subscription plan, and use the latest time as the updated subscription status of the first user for the agent.

[0062] Optionally, the status query module 200 is further configured to, after returning the subscription status to the agent, receive a subscription status update call request sent by the agent, wherein the subscription status update call request is sent by the agent after determining that the first user has permission to use the agent based on the subscription status and providing services to the first user; and update the first user's subscription status to the agent in response to the subscription status update call request.

[0063] Optionally, the state query module 200 is specifically used to receive a state query call request sent by the agent based on the Model Context Protocol (MCP) for calling the state query interface, wherein the input parameters for calling the state query interface include at least the user identifier of the first user. The subscription module 201 is specifically used to receive a subscription call request sent by the agent based on the MCP protocol when the agent determines that the first user does not have permission to use the agent according to the subscription status. The input parameters for calling the subscription interface include at least the user identifier of the first user.

[0064] This specification also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can be used to perform the above-described agent-based business execution method.

[0065] This specification also provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described agent-based business execution method.

[0066] based on Figure 1 The agent-based business execution method shown in this specification also provides embodiments that... Figure 3 The diagram shows the structure of the electronic device. Figure 3At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile storage, and may also include other hardware required for business operations. The processor reads the corresponding computer program from the non-volatile storage into memory and then runs it to implement the aforementioned agent-based business execution method.

[0067] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.

Claims

1. A business execution method based on intelligent agents, the method being applied to an intelligent agent management system, the method comprising: Receive status query request sent by the intelligent agent; The status query call request is sent by the intelligent agent when the first user uses the intelligent agent; Based on the user identifier of the first user carried in the status query call request, query the subscription status of the first user to the agent; Return the subscription status to the agent; Receive the subscription invocation request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent; In response to the subscription call request, query the pre-configured subscription plans associated with the agent and send each subscription plan to the first user; When a payment request is received from the first user for a target subscription plan among the subscription plans, the payment for the target subscription plan is made using the payment account corresponding to the first user's user identifier, and the first user's subscription status for the agent is updated.

2. The method as described in claim 1, before making payment for the target subscription plan using the payment account corresponding to the user identifier of the first user, the method further includes: Receive a payment account configuration request sent by the second user corresponding to the intelligent agent; Save the second user's payment account carried in the payment account configuration request, and establish the association between the smart agent and the payment account; Making payment for the target subscription plan using the payment account corresponding to the user identifier of the first user specifically includes: A payment order is created based on the payment account corresponding to the user identifier of the first user, the amount to be paid contained in the target subscription plan, and the receiving account associated with the smart agent; The payment account is used to make payment for the payment order.

3. The method as described in claim 1, wherein pre-configuring each subscription plan associated with the agent specifically includes: Receive a subscription plan configuration request sent by the second user corresponding to the intelligent agent; In response to the subscription plan configuration request, a subscription plan configuration page containing various preset subscription plan templates is returned to the second user; Acquire and store at least one subscription plan configured by the second user through the subscription plan configuration page, and establish the association between each acquired subscription plan and the intelligent agent.

4. The method as described in claim 3, wherein the subscription plan includes at least subscription rules and an amount to be paid; When the subscription rule includes available counts, update the first user's subscription status to the agent, specifically including: Add the available counts contained in the target subscription plan to the first user's current available counts for the agent, and use the updated current available counts as the updated subscription status of the first user for the agent; When the subscription rule includes available time, update the first user's subscription status to the agent, specifically including: Based on the current time and the available time included in the target subscription plan, determine the latest time at which the first user has the right to use the agent, and use the latest time as the updated subscription status of the first user to the agent.

5. The method of claim 1, after returning the subscription status to the agent, the method further includes: The system receives a subscription status update request sent by the agent, which is sent by the agent after determining that the first user has permission to use the agent based on the subscription status, and then provides services to the first user. In response to the subscription status update call request, the subscription status of the first user to the agent is updated.

6. The method as described in claim 1, wherein receiving a state query call request sent by the intelligent agent specifically includes: Receive a state query call request sent by the intelligent agent based on the Model Context Protocol (MCP) for calling the state query interface. The input parameters for calling the state query interface include at least the user identifier of the first user. Receiving the subscription invocation request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent, specifically includes: When the agent determines, based on the subscription status, that the first user does not have permission to use the agent, it receives a subscription call request sent based on the MCP protocol to invoke the subscription interface. The input parameters for invoking the subscription interface include at least the user identifier of the first user.

7. A business execution device based on an intelligent agent, the device being applied to an intelligent agent management system, the device comprising: The status query module is used to receive status query call requests sent by the intelligent agent; The status query call request is sent by the intelligent agent when the first user uses the intelligent agent; Based on the user identifier of the first user carried in the status query call request, query the subscription status of the first user to the agent; Return the subscription status to the agent; The subscription module is used to receive a subscription call request returned by the agent when it is determined from the subscription status that the first user does not have permission to use the agent; In response to the subscription call request, query the pre-configured subscription plans associated with the agent and send each subscription plan to the first user; The payment module is used to make payment for the target subscription plan using the payment account corresponding to the user identifier of the first user when it receives a payment request sent by the first user for the target subscription plan among the subscription plans, and to update the first user's subscription status for the agent.

8. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the method according to any one of claims 1-6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images