You must document your API, by using a YAML or a JSON file that follows the OpenAPI schema - for example, openapi.yaml. Make sure to host your API on a server that's accessible to the internet via HTTPS. You can implement this API any way you want, using your preferred server-side programming language. Your API exposes the endpoints that enable users to achieve the tasks they need to achieve with your plugin - for example, a real estate plugin defining a /get-listings endpoint. The part of your plugin that handles user actions is your API. The API, API specification, and plugin manifest are all hosted on your own server: For example, openapi.yaml.Ī plugin manifest, as a JSON file named ai-plugin.json, which is used by Microsoft Copilot to know when and how to use your plugin. Architecture of a pluginĪn API that runs on your own server, and which performs tasks.Īn API specification, as a YAML or JSON file, which describes your API by using the OpenAPI schema. Plugins can extend the capabilities of Microsoft Copilot by retrieving real-time information, to allow users to interact with the information in a natural way. However, Microsoft Copilot is unable to retrieve real-time information from third-party services. The large language model that powers Microsoft Copilot is trained on a wide range of data, which means that Microsoft Copilot can already understand and respond to a wide range of topics. For example, a plugin could retrieve the latest news and weather information, or let a user add or remove items in a to-do list. Plugins can retrieve information or perform tasks on behalf of a user. For Copilot for Microsoft 365, see Extend Microsoft Copilot for Microsoft 365.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |