Buildkite
Buildkite is a hybrid CI/CD platform that combines a hosted control plane (pipelines.buildkite.com) with self-hosted or Buildkite-Hosted agents that run jobs on customer-controlled infrastructure. The platform spans three core products — Pipelines, Test Engine, and Package Registries — and exposes them through a v2 REST API, a Relay-compliant GraphQL API at graphql.buildkite.com/v1, an Agent API at agent.buildkite.com/v3 consumed by the open-source Go agent, webhooks, and an official MCP server that surfaces those APIs to AI coding agents. Customers route work to specific agent pools through clusters and queues, define pipelines as YAML with dynamic uploads, and integrate with the major source control, cloud, identity, secrets, and observability vendors.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Buildkite the way a machine reads it — 117 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Buildkite scores 65.2/100 (strong), with a separate agent-readiness read of 33/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Buildkite's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/buildkite-com/"
title="Buildkite on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/buildkite-com.svg"
alt="Buildkite Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/buildkite-com/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/buildkite-com/"
title="Buildkite on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/buildkite-com/card.svg"
alt="Buildkite Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Buildkite
Each block below is one kind of artifact we hold for Buildkite. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 23
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Buildkite GraphQL API
GraphQL endpoint that returns deeply nested data on organizations, pipelines, builds, jobs, agents, clusters, queues, teams, audit events, suites, test executions, and package r...
Buildkite Agent API
Backplane consumed by the Buildkite Agent (open source, Go) to register, deregister, accept and finish jobs, upload artifacts, stream job logs, and emit metrics for cluster auto...
Buildkite Webhooks
Outbound HTTP notifications fired in response to build, job, agent, ping, deployment, and package events across Pipelines, Test Engine, and Package Registries. Verified with the...
Buildkite MCP Server
Official Model Context Protocol server that exposes Buildkite REST API surfaces (pipelines, builds, jobs, agents, artifacts, annotations) as MCP tools and toolsets for AI coding...
Buildkite Access Token API
The Access Token API from Buildkite — 1 operation(s) for access token.
Buildkite Agent Tokens API
The Agent Tokens API from Buildkite — 1 operation(s) for agent tokens.
Buildkite Agents API
The Agents API from Buildkite — 3 operation(s) for agents.
Buildkite Annotations API
The Annotations API from Buildkite — 1 operation(s) for annotations.
Buildkite Artifacts API
The Artifacts API from Buildkite — 1 operation(s) for artifacts.
Buildkite Builds API
The Builds API from Buildkite — 4 operation(s) for builds.
Buildkite Clusters API
The Clusters API from Buildkite — 1 operation(s) for clusters.
Buildkite Emojis API
The Emojis API from Buildkite — 1 operation(s) for emojis.
Buildkite Jobs API
The Jobs API from Buildkite — 2 operation(s) for jobs.
Buildkite Meta API
The Meta API from Buildkite — 1 operation(s) for meta.
Buildkite Metrics API
The Metrics API from Buildkite — 1 operation(s) for metrics.
Buildkite Organizations API
The Organizations API from Buildkite — 2 operation(s) for organizations.
Buildkite Pipeline Templates API
The Pipeline Templates API from Buildkite — 1 operation(s) for pipeline templates.
Buildkite Pipelines API
The Pipelines API from Buildkite — 2 operation(s) for pipelines.
Buildkite Queues API
The Queues API from Buildkite — 1 operation(s) for queues.
Buildkite Rules API
The Rules API from Buildkite — 1 operation(s) for rules.
Buildkite Stacks API
The Stacks API from Buildkite — 1 operation(s) for stacks.
Buildkite Teams API
The Teams API from Buildkite — 1 operation(s) for teams.
Buildkite User API
The User API from Buildkite — 1 operation(s) for user.
Scroll within the panel for all 23 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Buildkite REST API
POSTMANOpen Collections 22
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONBuildkite Agent API
OPEN COLLECTIONBuildkite Agent Access Token API
OPEN COLLECTIONBuildkite Agent Access Token Agent Tokens API
OPEN COLLECTIONBuildkite Agent Access Token Agents API
OPEN COLLECTIONBuildkite Agent Access Token Annotations API
OPEN COLLECTIONBuildkite Agent Access Token Artifacts API
OPEN COLLECTIONBuildkite Agent Access Token Builds API
OPEN COLLECTIONBuildkite Agent Access Token Clusters API
OPEN COLLECTIONBuildkite Agent Access Token Emojis API
OPEN COLLECTIONBuildkite Agent Access Token Jobs API
OPEN COLLECTIONBuildkite Agent Access Token Meta API
OPEN COLLECTIONBuildkite Agent Access Token Metrics API
OPEN COLLECTIONBuildkite Agent Access Token Organizations API
OPEN COLLECTIONBuildkite Agent Access Token Pipeline Templates API
OPEN COLLECTIONBuildkite Agent Access Token Pipelines API
OPEN COLLECTIONBuildkite Agent Access Token Queues API
OPEN COLLECTIONBuildkite Agent Access Token Rules API
OPEN COLLECTIONBuildkite Agent Access Token Stacks API
OPEN COLLECTIONBuildkite Agent Access Token Teams API
OPEN COLLECTIONBuildkite Agent Access Token User API
OPEN COLLECTIONBuildkite REST API
OPEN COLLECTIONScroll within the panel for all 22 ·
Arazzo Workflows 9
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Buildkite Build Failure Triage
Inspect a finished build, then pull its annotations and artifacts for triage.
ARAZZOBuildkite Collect Build Artifacts
Look up a build, confirm it finished, then list its artifacts.
ARAZZOBuildkite Provision Pipeline And First Build
Create a pipeline in an organization, then trigger its first build.
ARAZZOBuildkite Rebuild Latest Build
Find the most recent build on a pipeline, rebuild it, then poll the new build.
ARAZZOBuildkite Retry Failed Job
Find a failed job in a build, retry it, then poll the build to completion.
ARAZZOBuildkite Stop Disconnected Agent
List agents, inspect one, and stop it when it is no longer connected.
ARAZZOBuildkite Trigger And Poll Build
Create a build on a pipeline, then poll until it reaches a terminal state.
ARAZZOScroll within the panel for all 9 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Buildkite MCP Server
Buildkite operates an official Model Context Protocol server that exposes the REST API (organizations, clusters, agents, pipelines, builds, jobs, artifacts, annotations, logs, T...
MCP SERVERGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Buildkite GraphQL API
GraphQL endpoint that returns deeply nested data on organizations, pipelines, builds, jobs, agents, clusters, queues, teams, audit events, suites, test executions, and package r...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Buildkite Com Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Buildkite Com Finops
FINOPSFeatures 23
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 23 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Buildkite Com Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Buildkite API Rules
SPECTRALBuildkite API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Buildkite Com Pipeline Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Integrations 19
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Scroll within the panel for all 19 ·
Resources
Every other property we hold for Buildkite — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 16
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 16 ·
Build 16
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 16 ·
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 7
Status, limits, changes, and where to get help
Scroll within the panel for all 7 ·
Commercial 5
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/buildkite-com · machine-readable index on apis.io
This is an independent, third-party profile of Buildkite, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.