Skill: Implement Auth.md Agent Registration Discovery
What This Skill Does
Helps a service publish Auth.md support for agent registration. Use this when a scanner reports the authMd check is failing or when adding the Auth.md standard to an API or application.
Requirements
- Serve
/auth.mdfrom the service root as Markdown with an H1 heading that containsauth.md(for example,# auth.mdor# Example auth.md). - Prefer publishing OAuth Protected Resource Metadata at
/.well-known/oauth-protected-resourcefor the resource server. - Include
resource,authorization_servers,scopes_supported, andbearer_methods_supportedwithheaderin the PRM document. - Publish OAuth Authorization Server metadata at each advertised authorization server's
/.well-known/oauth-authorization-serverURL. - Include a valid
issuerin Authorization Server metadata and ensure it matches the issuer advertised in PRM. - Add an
agent_authblock withskill,register_uri, and at least one complete registration method when Authorization Server metadata is available. - If OAuth metadata is not available, keep
/auth.mdself-contained: identify the agent audience, document registration or provisioning endpoint(s), list supported method(s), and explain credential use.
Flow Metadata
- ID-JAG: include
identity_types_supported: ["identity_assertion"],identity_assertion.assertion_types_supportedwithurn:ietf:params:oauth:token-type:id-jag, and credential types. Includerevocation_uriand the revocation event inevents_supportedwhen supported. - Verified email: include
identity_assertion.assertion_types_supportedwithverified_email, credential types, andclaim_uri. - Anonymous: include
identity_types_supported: ["anonymous"],anonymous.credential_types_supported, andclaim_uri.
Validate
POST https://isitagentready.com/api/scan
Content-Type: application/json
{"url": "https://YOUR-SITE.com"}
Check that checks.discovery.authMd.status is "pass".