The agent uses the Get Build Artifacts capability with a specific job ID. When a developer asks about build outputs, the agent calls AppVeyor's API to retrieve the list of artifacts for that job, including compiled binaries, test results, and deployment packages.

Yes. The agent can retrieve all projects configured in your AppVeyor account using the Get Projects capability. This gives you visibility into all your build pipelines, repository connections, and project configurations through conversation.

The agent can enumerate all deployment environments in your AppVeyor account. This includes environment names, configurations, and settings, helping DevOps teams understand available deployment targets before triggering releases.

AppVeyor uses bearer token authentication. You provide your API token from AppVeyor's API token page in the Tars dashboard. The agent then includes this token in the Authorization header for all API requests to AppVeyor.

Yes. The agent can retrieve all users and roles in your account, plus inspect detailed permissions for specific roles. This enables security teams to conduct access audits and verify team permissions through natural conversation.

AppVeyor is built for Windows developers and supports Windows, Linux, and macOS builds. The agent can access project and artifact information regardless of the build platform, giving you visibility into all your CI/CD pipelines.

The agent can list all roles in your account and retrieve detailed information about specific roles by ID. This includes role permissions, metadata, and configuration, enabling thorough access control reviews.

Yes. When you provide a job ID, the agent retrieves the complete list of artifacts for that build job. This helps developers quickly locate compiled binaries, test outputs, and deployment packages from specific CI/CD runs.