Search Agentized Websites

Treat Agentize as a publisher-controlled HTTP interface. The target agent does not need the Agentize package or its source code.

Detect Agentize

Given a website origin, request GET <origin>/agents with Accept: application/json.

Call the site Agentized only when all of these hold:

• The response is successful JSON, not an HTML page or redirect destination masquerading as discovery.
• version is a supported protocol version; this skill supports 0.1.
• site contains a non-empty name, origin, and description.
• index, search, and resources are URL strings; the resources value contains {id}.
• Resolved endpoints use HTTP(S) and remain on the declared site origin. Do not follow a manifest to another origin unless the user explicitly authorizes it.

A 404, authentication challenge, HTML response, malformed manifest, unsupported version, or network failure means “Agentize not detected,” with the reason. It does not prove the site can never be Agentized. Do not probe invented alternative paths, crawl pages, or use llms.txt as evidence of Agentize.

For terminal work, use the dependency-free helper: