Red Hat is Poor to agents.

Item: Red Hat API
Rating: 43
Author: Discry

Discry independently scored how well an AI agent can discover and understand the Red Hat API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.

Discry your API — free View the docs ↗

SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.

Discovery

45% of score · 40/100

OpenAPI specA machine-readable OpenAPI/Swagger spec agents can parse.Partial

llms.txtAn llms.txt index that points agents to the docs that matter.Fail

llms.txt qualityThe llms.txt is focused, current, and well under the size budget.Fail

llms-full.txtA full-text bundle agents can load in one request.Fail

AGENTS.mdAn AGENTS.md that tells coding agents how to build on the API.Fail

.well-known/mcp.jsonA discoverable MCP manifest at a well-known path.Fail

MCP registryThe API is listed in a public MCP registry.Pass

robots.txt AI directivesrobots.txt allows (or explicitly guides) AI crawlers.Pass

SitemapA sitemap so agents can enumerate the docs surface.Pass

Comprehension

55% of score · 46/100

Task-oriented descriptionsEndpoints described by what they accomplish, not just their shape.Partial

Realistic examplesRunnable, real-world request/response examples.Partial

Multi-step workflowsDocs that chain calls into complete jobs an agent can follow.Partial

Error-recovery guidanceDocumented failure modes and how to recover from them.Partial

Answer-first formatThe answer leads; preamble does not bury it.Partial

Capability boundariesClear limits — what the API can and cannot do.Partial

Naming consistencyConsistent, predictable naming across endpoints.Partial

Heading hierarchyClean heading structure agents can navigate.Partial

Markdown docsDocs available as clean markdown, not JS-rendered HTML only.Partial

Token efficiencyDocs are concise enough to fit an agent context window.Fail

What we found

Red Hat has an official MCP server (Lightspeed) on both PulseMCP and Glama for AI-assisted RHEL infrastructure management
The developer portal is primarily a content/article hub rather than a unified API reference, making agent discovery difficult
OpenAPI specs exist for specific products (ACS, 3scale) but no unified spec index
robots.txt has no AI bot restrictions but also no explicit AI-welcome signals
Documentation quality varies significantly across Red Hat products — some excellent, others sparse

What to change

Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.

01Add llms.txt to developers.redhat.com covering key API products (OpenShift, ACS, 3scale)
02Create a unified API reference page linking to all product-specific OpenAPI specs
03Add AGENTS.md to RedHatOfficial GitHub org with guidance for coding agents
04Standardize documentation format across products for consistent agent consumption
05Add .well-known/mcp.json pointing to the Lightspeed MCP server

Execution coverage · INFORMATIONAL, UNSCORED

Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.

OAuth2API keyservice account✓ Error format documented✓ Rate limits documented✓ Pagination documented✕ Idempotency documented

Red Hat documents various auth methods across products. The ACS API has OpenAPI 3.0 spec. Error formats and rate limits documented per product. Pagination varies by API.

See your own Discry Score.

Drop your API docs URL. See what an agent sees — in 60 seconds, free.

Discry your API — free