Poppy Validator

Checks Personal Agent Protocol discovery documents against the specification (Draft 0.1, Draft 0.2), so a Company or a Personal Agent can find a problem before the other side runs into it. What each message means.

A Company's domain checks its poppy.json and OAuth server metadata. A Personal Agent's client_id URL checks its client metadata and keys.

Use it from code

curl -s https://poppydemoagent.dev/validator/api -H 'Content-Type: application/json' \
  -d '{"url": "example.com"}'

Or post a document: {"document": "{…}", "kind": "poppy", "domain": "example.com"}. The response is the JSON report described on the messages page. Errors break a requirement (a MUST, an RFC's MUST, or a normative rule without a key word); warnings depart from a recommendation (a SHOULD, the Guides) or our reading of an open question; info is worth knowing but harmless. Each message names its basis, and the report says separately whether our own agent refuses the documents.