Configure Agent Headers

Use this skill to expose well-known agentic endpoints natively via HTTP response headers (RFC 8288 Link headers) and DNS Service Bindings (DNS-AID). This is the lowest-friction way to declare agent-readiness — no routing changes, no new pages, just headers and optional DNS records.

Core Rules

• Serve Link: </.well-known/...>; rel="..." headers on all primary responses (especially GET /).
• Link header format MUST conform to RFC 8288 — use rel types that match the agentic discovery spec.
• DNS-AID SVCB records are optional but recommended for domain operators who want DNS-level discoverability.
• Headers must be set at the edge or CDN level — do not rely solely on origin application code which may not apply to all routes.
• Do not expose internal-only endpoints via Link headers. Only publicly accessible discovery endpoints.
• Verify that every URL in a Link header is on a domain the operator controls; third-party URLs in Link headers can enable agent phishing (OWASP ASI01)
• Do not place credentials, tokens, or PII in Link header values; Link headers are publicly cacheable
• Treat the Link header itself as a discovery contract: schema-drift between the declared rel and the served payload must be rejected by the scanner (OWASP ASI04)

When to Use