Buildkite
Buildkite is a CI/CD platform with self-hosted agents and a hosted control plane. The platform exposes a REST API, a GraphQL API and an Agent API used by buildkite-agent. Resources include organizations, pipelines, pipeline templates, builds, jobs, agents, clusters, queues, teams, rules, artifacts, annotations, and access tokens. Test Engine adds test execution and analytics endpoints.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Buildkite the way a machine reads it — 29 machine-readable artifacts across 20 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 45.5/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
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 20
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 REST API
JSON over HTTPS REST API for the Buildkite control plane. Bearer-token auth with API access tokens.
Buildkite GraphQL API
Relay-compliant GraphQL API. Single endpoint for nested queries across organizations, pipelines, builds, jobs, agents, teams. Introspection supported. Bearer auth with the "Enab...
Buildkite Agent API
API consumed by buildkite-agent — register, retrieve work, send job events and upload artifacts/annotations. Used by self-hosted and hosted agents.
Buildkite AccessToken API
The AccessToken API from Buildkite — 1 operation(s) for accesstoken.
Buildkite Agents API
The Agents API from Buildkite — 5 operation(s) for agents.
Buildkite AgentTokens API
The AgentTokens API from Buildkite — 2 operation(s) for agenttokens.
Buildkite Annotations API
The Annotations API from Buildkite — 2 operation(s) for annotations.
Buildkite Artifacts API
The Artifacts API from Buildkite — 4 operation(s) for artifacts.
Buildkite Builds API
The Builds API from Buildkite — 6 operation(s) for builds.
Buildkite Clusters API
The Clusters API from Buildkite — 2 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 — 5 operation(s) for jobs.
Buildkite Meta API
The Meta API from Buildkite — 1 operation(s) for meta.
Buildkite Organizations API
The Organizations API from Buildkite — 4 operation(s) for organizations.
Buildkite Pipelines API
The Pipelines API from Buildkite — 5 operation(s) for pipelines.
Buildkite PipelineTemplates API
The PipelineTemplates API from Buildkite — 2 operation(s) for pipelinetemplates.
Buildkite Queues API
The Queues API from Buildkite — 4 operation(s) for queues.
Buildkite Rules API
The Rules API from Buildkite — 2 operation(s) for rules.
Buildkite Teams API
The Teams API from Buildkite — 2 operation(s) for teams.
Buildkite User API
The User API from Buildkite — 1 operation(s) for user.
Scroll within the panel for all 20 ·
Open Collections 1
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).
Buildkite REST API
OPEN COLLECTIONGraphQL 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
Relay-compliant GraphQL API. Single endpoint for nested queries across organizations, pipelines, builds, jobs, agents, teams. Introspection supported. Bearer auth with the "Enab...
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 six things the Kin Score reads for commercial clarity.
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 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 Finops
FINOPSSecurity 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.
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.
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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/buildkite · machine-readable index on apis.io