Reference guides for the developer apps an AI agent can work with: every endpoint, the permission each one needs, and how to give agents safe, governed access.
The Better Stack API is how an app or AI agent works with a Better Stack team: listing monitors, creating an incident that pages the on-call person, acknowledging or resolving an active incident, or managing heartbeats and status pages.
The Bitbucket API is how an app or AI agent works with a Bitbucket Cloud workspace: reading repositories and commits, opening and merging pull requests, creating and updating issues, and running build pipelines.
The BugSnag API is how an app or AI agent works with a BugSnag account: listing the errors on a project, reading the events behind an error, resolving errors, and tracking releases and stability over time.
The CircleCI API is how an app or AI agent works with a CircleCI account: triggering a pipeline, reading the workflows and jobs inside it, canceling or rerunning a workflow, and managing the contexts and environment variables that builds use.
The Cloudflare API is how an app or AI agent works with a Cloudflare account: editing DNS records, purging cached content, deploying Workers scripts, and tuning firewall and WAF rules.
The Datadog API is how an app or AI agent works with a Datadog account: submitting and querying metrics, creating and editing monitors, searching logs, opening incidents, and reading the hosts that report in.
The DigitalOcean API is how an app or AI agent works with a DigitalOcean account: listing and creating Droplets, rebooting or resizing a server, spinning up Kubernetes clusters and databases, and editing domains and DNS records.
The Docker Hub API is how an app or AI agent works with a Docker Hub account: listing and creating repositories, reading the tags published to an image, managing access tokens, and reviewing an organization's members and audit log.
The Fly.io API is how an app or AI agent runs infrastructure on Fly.io: creating and deleting apps, launching virtual machines from a Docker image, starting, stopping, and restarting them, and attaching persistent volumes.
The Gitea API is how an app or AI agent works with a Gitea instance: reading and creating repositories, filing and editing issues, opening and merging pull requests, and reading or writing files in a repository.
The GitHub API is how an app or AI agent works with a GitHub account: reading and creating repositories, opening and merging pull requests, filing and updating issues, and triggering workflow runs.
The GitLab API is how an app or AI agent works with a GitLab project: reading and creating issues, opening and merging merge requests, reading and writing repository files, and triggering CI/CD pipelines.
The Grafana API is how an app or AI agent works with a Grafana instance: reading and saving dashboards, organizing folders, managing data sources and alert rules, and adding annotations to charts.
The Heroku API is how an app or AI agent works with a Heroku account: creating and updating apps, scaling and restarting the dynos that run them, deploying releases and rolling them back, and provisioning add-ons like databases.
The Honeycomb API is how an app or AI agent works with a Honeycomb account: sending telemetry events to a dataset, running a query, building a board, and setting a trigger or an SLO that watches the data.
The Jenkins API is how an app or AI agent works with a Jenkins controller: reading a job and its builds, triggering a build with or without parameters, fetching console output, and creating, copying, or deleting jobs.
The JFrog Artifactory API is how an app or AI agent works with a binary repository: deploying and downloading artifacts, creating and configuring repositories, searching with the Artifactory Query Language, and publishing and promoting builds.
The LaunchDarkly API is how an app or AI agent works with a LaunchDarkly account: listing feature flags, turning a flag on or off in an environment, editing the segments that decide who a flag targets, and reading experiments and the audit log.
The Linear API is how an app or AI agent works with a Linear workspace: listing and filing issues, moving them through workflow states, commenting on them, and reading projects, teams, and cycles.
The Make API is how an app or AI agent works with a Make organization: listing and running scenarios, reading their execution logs, managing the connections to outside apps, and reading and writing records in data stores.
The n8n API is how an app or AI agent works with an n8n instance: listing and creating workflows, activating and deactivating them, reading and retrying executions, and managing credentials, tags, users, and projects.
The Netlify API is how an app or AI agent works with a Netlify account: listing and creating sites, starting builds, publishing and restoring deploys, reading form submissions, and managing DNS records and environment variables.
The New Relic API is how an app or AI agent works with a New Relic account: running NRQL queries over telemetry, searching monitored entities, creating alert policies and dashboards, and sending in metrics, events, and logs.
The npm API is how an app or AI agent works with the npm registry: reading a package's metadata, searching for packages, publishing new versions, and moving distribution tags like latest or beta.
The Opsgenie API is how an app or AI agent works with an Opsgenie account: raising and closing alerts, acknowledging and assigning them, opening incidents, reading who is on call right now, and pinging heartbeats.
The PagerDuty API is how an app or AI agent works with an on-call account: listing and creating incidents, acknowledging or resolving them, adding notes, and reading who is on call across schedules and escalation policies.
The Postman API is how an app or AI agent works with a Postman account: listing and editing collections, managing environments and workspaces, reading API definitions, and running mock servers and monitors.
The Railway API is how an app or AI agent works with a Railway account: listing projects, creating a service, triggering and rolling back deployments, and reading or setting a service's environment variables.
The Render API is how an app or AI agent manages a Render account: listing and creating services, triggering and rolling back deploys, setting environment variables, and provisioning Postgres and Key Value databases.
The Rollbar API is how an app or AI agent works with a Rollbar project: reporting errors as occurrences, listing and reading the items those occurrences group into, marking an item resolved or muted, recording deploys, and querying error trends.
The Sentry API is how an app or AI agent works with a Sentry organization: listing and triaging the issues an application is reporting, reading the underlying error events, creating and updating projects, and recording releases and their deploys.
The Snyk API is how an app or AI agent works with a Snyk account: listing the projects in an organization, reading the security issues a scan found, generating a software bill of materials for a project, and searching the audit log of who did what.
The Sourcegraph API is how an app or AI agent works with a code intelligence instance: searching code across every connected repository, reading files, looking up users and organizations, and running large-scale code changes.
The Statuspage API is how an app or AI agent runs a status page: opening and updating incidents, flipping a component to a degraded or operational status, adding metric data points, and managing the subscribers who get notified.
The Terraform Cloud API is how an app or AI agent works with an organization's infrastructure: listing and locking workspaces, queuing a run, applying or cancelling it, reading state versions, and managing variables and projects.
The Vercel API is how an app or AI agent works with a Vercel account: creating and canceling deployments, reading and updating projects, managing domains and DNS records, and setting environment variables.
The Workato API is how an app or AI agent works with a Workato workspace: listing and starting recipes, reading a recipe's job runs, creating and updating connections, organizing folders and projects, and reading and writing lookup table rows.
Bollard AI sits between a team's AI agents and the apps it runs on. Grant each agent exactly the access it needs, read or write, app by app, and every call is checked and logged.