buildkite.com agentic web readiness

C Manifest validity: 100% (2/2 valid, 0 errors, 4 warnings) · Surface score 25 (coverage 10 + breadth 0 + conformance 15). 2 standards observed across 1 of 9 steps; 2 manifests present (+ robots.txt), 0 errors, 4 warnings. Checked 2026-10-25 13:55:56 UTC. This grades the agent-facing files published at buildkite.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/buildkite.com.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

What an agent can call

• MCP endpoint https://mcp.buildkite.com/mcp (streamable-http) — from /.well-known/ard.json
• MCP endpoint https://mcp.buildkite.com/mcp (streamable-http) — from /.well-known/ai-catalog.json
• llms.txt: Buildkite Documentation, 273 links
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)
• ARD bridge (/.well-known/ard.json): 0/1 valid, 0 legacy, 0 dead/broken

Standards observed

• Agentic Resource Discovery https://buildkite.com/.well-known/ard.json
• AI Catalog well-known file https://buildkite.com/.well-known/ai-catalog.json

Cheapest next steps

1. llms.txt: one Markdown index file; the most widely read agent-facing file
   Generate starter /llms.txt for buildkite.com

   # Buildkite
   
   > Buildkite and what it offers to agents
   
   Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.
   
   ## Docs
   - [Getting started](https://buildkite.com/docs/getting-started): the first page to read
   - [API reference](https://buildkite.com/openapi.json): OpenAPI description
   
   ## Optional
   - [Changelog](https://buildkite.com/changelog): what changed, newest first
   

2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for buildkite.com

   # Buildkite for agents
   
   Buildkite and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://buildkite.com/llms.txt
   - API description: https://buildkite.com/openapi.json
   - Discovery catalog: https://buildkite.com/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://buildkite.com/mcp
   - Rate limits and authentication: describe them here
   
   ## Conventions
   - How to cite or attribute content
   - What not to do (no scraping of /account/, no automated sign-ups, etc.)
   
   Contact: security@buildkite.com
   

3. api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "buildkite.com"}))

Agent pre-flight & practical readiness

Preferred mode: mcp. Call the MCP endpoint at https://mcp.buildkite.com/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://mcp.buildkite.com/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 180114 (~176 KB of head/script markup before main text), HTML-to-llms.txt token ratio 5.649×.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 19/20, readability 20/30, capabilities 15/35, conformance 15/15, total 69/100, grade A.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules