Buildkite API
68
AI ReadinessAI-Aware (B+)68/100
Agent-ready OpenAPI document · curated by JenticDeveloper ToolsCi Cdbearer18 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Trigger builds, manage pipelines, and inspect agents inside a Buildkite organisation across 18 REST endpoints.
Use for: I need to trigger a Buildkite build on the main branch, Cancel a Buildkite build that is stuck, List all pipelines inside my Buildkite organisation, Rebuild a previous Buildkite run after a flaky failure
Not supported: Does not handle build artefact storage, agent installation on hosts, or test result reporting - use for managing pipelines, triggering and inspecting builds, and listing agents only.
Jentic publishes the only available OpenAPI specification for Buildkite API, keeping it validated and agent-ready. Buildkite is a CI/CD platform that runs build jobs on customer-controlled agents while providing a hosted control plane for organisations, pipelines, builds, and self-hosted agents. The v2 REST API covers the operator surface: listing and managing pipelines, triggering and cancelling builds, rebuilding past runs, and inspecting connected agents. Use it to script pipeline provisioning, kick off ad-hoc deploys, surface build status in a custom dashboard, or wire CI events into chat and incident tools.
Install Jentic One Beta
Connect the Buildkite API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Buildkite API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbuildkite.com%2Fbuildkite" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbuildkite.com%2Fbuildkite" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Buildkite API.
List, create, update, and delete pipelines inside a Buildkite organisation
Trigger a new build on a pipeline with a commit SHA, branch, and message
List builds across the whole account, an organisation, or a single pipeline
Cancel an in-flight build or rebuild a previously completed build
List connected agents and stop a specific agent gracefully
Read organisation metadata and the current authenticated user profile
Inspect a specific build by pipeline slug and build number
Use Cases
Patterns agents use Buildkite API for, with concrete tasks.
★ ChatOps Deploy Triggers
Let engineers trigger releases from Slack with a slash command. The agent translates the command into a POST /organizations/{org_slug}/pipelines/{pipeline_slug}/builds call, supplies the branch and commit, and replies with the build URL. Combined with the cancel and rebuild endpoints it covers the full deploy controls without anyone touching the dashboard.
Trigger a build on the deploy-prod pipeline at branch main with commit SHA abc123 and message Manual deploy from Slack.
Pipeline Provisioning at Scale
Create Buildkite pipelines programmatically when new repositories are onboarded. POST /organizations/{org_slug}/pipelines accepts pipeline YAML and repository URL so a script can spin up CI for every new service. Pair it with PATCH to update steps as the standard pipeline template evolves across the organisation.
Create a Buildkite pipeline named payments-service in the example-org organisation, pointing at github.com/example/payments-service with the standard build steps.
Build Health Dashboard
Power a custom dashboard that surfaces flaky pipelines and long-running builds. Poll GET /organizations/{org_slug}/builds with state filters, group by pipeline, and compute pass rate and median duration. Use the rebuild endpoint to retry suspected flakes automatically and tag the rebuild reason in the message.
List all builds in the last 24 hours, group by pipeline, and post the top 3 pipelines with the most failures to a Slack channel.
AI Agent Release Captain via Jentic
An on-call agent connected via Jentic can act as a release captain - triggering builds, cancelling ones that fail review, and confirming the rebuild succeeded. The agent searches Jentic for trigger a build, loads the POST .../builds schema, and executes against the operator's vault-stored Buildkite token without ever exposing the secret.
Search Jentic for trigger a Buildkite build, load the schema, execute it for pipeline deploy-prod on branch main, and poll until the build state is passed or failed.
Key Endpoints
18 endpoints — jentic publishes the only available openapi specification for buildkite api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/organizations/{org_slug}/pipelines/{pipeline_slug}/builds
Create a build
PUT
/organizations/{org_slug}/pipelines/{pipeline_slug}/builds/{build_number}/cancel
Cancel a build
PUT
/organizations/{org_slug}/pipelines/{pipeline_slug}/builds/{build_number}/rebuild
Rebuild a build
POST
/organizations/{org_slug}/pipelines
Create a pipeline
GET
/organizations/{org_slug}/builds
List builds in an organisation
GET
/organizations/{org_slug}/agents
List agents
PUT
/organizations/{org_slug}/agents/{agent_id}
Stop an agent
POST
/organizations/{org_slug}/pipelines/{pipeline_slug}/builds
Create a build
PUT
/organizations/{org_slug}/pipelines/{pipeline_slug}/builds/{build_number}/cancel
Cancel a build
PUT
/organizations/{org_slug}/pipelines/{pipeline_slug}/builds/{build_number}/rebuild
Rebuild a build
POST
/organizations/{org_slug}/pipelines
Create a pipeline
GET
/organizations/{org_slug}/builds
List builds in an organisation
GET
/organizations/{org_slug}/agents
List agents
PUT
/organizations/{org_slug}/agents/{agent_id}
Stop an agent
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
B
Buildkite API
- AI-Aware (B+)68/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
29%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Buildkite by hand means learning its bearer token auth against api.buildkite.com/v2 and passing the organization and pipeline slugs through every build call yourself. Through Jentic you install once, import Buildkite from the API Directory, store the token once, and your agent calls it.
Permission scoping
Buildkite puts the organization and pipeline slugs in the URL path (/organizations/{org_slug}/pipelines/{pipeline_slug}/builds/...), so a rule can pin your agent to one pipeline: it can trigger, cancel, and rebuild builds there and nothing else. You choose the operations it may call, so it can trigger builds without being able to create new pipelines or update agents unless you add those.
Credential isolation
Your Buildkite API access token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'trigger a build' or 'cancel a build', and Jentic returns the matching Buildkite operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Buildkite API through Jentic.
Why is there no official OpenAPI spec for Buildkite API?
Buildkite documents its REST API in human-readable form but does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Buildkite API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Buildkite API use?
Buildkite uses HTTP bearer authentication with an API access token generated from your personal settings. Each request must include Authorization: Bearer <token>. Through Jentic, the token is stored encrypted in the vault and the header is constructed at execution time.
Can I trigger a Buildkite build through the API?
Yes. POST /organizations/{org_slug}/pipelines/{pipeline_slug}/builds creates a new build with parameters for branch, commit SHA, message, and environment variables. The response includes the build number and URL so you can poll its status afterwards.
Can I cancel or rebuild a Buildkite build through the API?
Yes. PUT /organizations/{org_slug}/pipelines/{pipeline_slug}/builds/{build_number}/cancel cancels an in-flight build, and PUT on the same path with /rebuild retries a completed build. Both return the updated build resource.
What are the rate limits for the Buildkite API?
Buildkite enforces per-token rate limits that are not encoded in the OpenAPI spec. Add retry-with-backoff for HTTP 429 responses and avoid tight polling on the builds endpoints - prefer webhooks for build state change notifications when possible.
How do I trigger a Buildkite build from an AI agent through Jentic?
Run pip install jentic and authenticate with your ak_* key. Search Jentic with trigger a Buildkite build, load the POST .../builds operation, and execute it with org_slug, pipeline_slug, branch, and commit. Jentic injects the bearer token from your stored credential.
Can I limit what my agent is allowed to do with the Buildkite API?
Yes. Because Jentic One runs self-hosted, your own rules decide which Buildkite operations and credentials the agent may use. Buildkite puts the organization and pipeline slugs in the URL path, so a rule can pin the agent to a single pipeline where it may trigger, cancel, and rebuild builds and nothing else. You choose the exact operations it can call, so it can trigger builds without also being able to create new pipelines or stop agents unless you grant those.
GET STARTED