docs.sentry.io agentic web readiness

B Manifest validity: 50% (2/4 valid, 2 errors, 2 warnings) · Surface score 31 (coverage 20 + breadth 6 + conformance 5). 4 standards observed across 2 of 9 steps; 4 manifests present (+ robots.txt), 2 errors, 2 warnings. Checked 2026-10-25 23:41:39 UTC. This grades the agent-facing files published at docs.sentry.io, not the organisation's products.

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

Coverage by step

Manifests

# Authenticating to Docs as an agent

This file is the agent-auth skill for docs.sentry.io. It is linked from the authorization server's metadata (`agent_auth.skill`).

## Discovery
1. Call the API. A `401` carries `WWW-Authenticate: Bearer resource_metadata="https://docs.sentry.io/.well-known/oauth-protected-resource"`.
2. Read `/.well-known/oauth-protected-resource` (RFC 9728) for `resource` and `authorization_servers`.
3. Read the authorization server's `/.well-known/oauth-authorization-server` (RFC 8414); the `agent_auth` block lists the endpoints below.

## Methods we accept
- `identity_assertion`: you hold a session for a user and can mint an ID-JAG with `aud` = our `resource`. Preferred.
- `service_auth`: you only know the user's email. A claim ceremony (6-digit code) is required.
- `anonymous`: no user. Immediate limited scopes; the user can claim later.

## Register
POST `agent_auth.identity_endpoint` with `{"type": "<method>", ...}`; exchange the returned `identity_assertion` at the token endpoint for an access token.

## Scopes
- `api.read`: read
- `api.write`: write (claimed registrations only)

## Rules
- Show the user our name and the scopes before asserting their identity.
- Keep `claim_token` in memory only.
- Revocation events arrive as Security Event Tokens at your registered events endpoint.

---
okf_version: "0.2"
title: "Docs Knowledge Bundle"
description: "Docs and what it offers to agents"
---

# Docs Knowledge Bundle

> Docs and what it offers to agents

- [Update Log](log.md)

## Concepts

- [Docs Overview](concepts/docs.md) — Docs and what it offers to agents

What an agent can call

• llms.txt: Sentry Documentation, 126 links
• OKF bundle (/okf/index.md): Page Not Found, 2 concept links
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed

Standards observed

• llms.txt https://docs.sentry.io/llms.txt
• AGENTS.md https://docs.sentry.io/AGENTS.md
• Content Signals Policy https://docs.sentry.io/robots.txt
• Markdown for Agents https://docs.sentry.io/

Cheapest next steps

1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "docs.sentry.io"}))
2. 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": "docs.sentry.io"}))
3. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
   Generate starter /.well-known/security.txt for docs.sentry.io

   Contact: mailto:security@docs.sentry.io
   Expires: 2027-09-20T23:41:39Z
   Canonical: https://docs.sentry.io/.well-known/security.txt
   Preferred-Languages: en
   Policy: https://docs.sentry.io/security-policy
   

Agent pre-flight & practical readiness

Preferred mode: llms_txt (fallback markdown_negotiation). GET /llms.txt and follow the links it names. That index is the page list an agent should read.

Fetch: GET https://docs.sentry.io/llms.txt GET /llms.txt and follow its links.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0, HTML-to-llms.txt token ratio 1.322×.

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

Readiness subscores: reach 20/20, readability 28/30, capabilities 6/35, conformance 5/15, total 59/100, grade B.

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