PAP discovery report
prijsprofeet.be
Publishes a poppy.json with no problems found. Organization: PrijsProfeet.
Publishes poppy.json
0problems
HTTP 200 Version 0.3 Routes APIs Checked 18 hours ago
First seen 2 Nov 2026
Draft 0.3 of the Personal Agent Protocol is still in progress: it is not published or frozen, and its text is still changing. These results follow draft 0.3 as written on 2 November 2026, and will change when the draft does.
Findings10 passed · 1 note · 19 skipped
Results from the Personal Agent Protocol's official Company validator, commit 7205250, draft 0.3 (read-only survey + file check).
Discovery
Note
Draft 0.3 is still in progress
Draft 0.3 is not published or frozen yet, and its text is still changing. These results follow it as written on 2 November 2026, and may change when the draft does.
§1
OK
poppy.json is served over HTTPS at the well-known path
Served at https://www.prijsprofeet.be/.well-known/poppy.json after 1 redirect(s).
discovery.https
§3
OK
Every redirect of the well-known URL is to an HTTPS URL
Redirects: https://prijsprofeet.be/.well-known/poppy.json → 301, https://www.prijsprofeet.be/.well-known/poppy.json → 200.
discovery.redirects-https
§3
OK
Redirects of the well-known URL end at /.well-known/poppy.json, with no query
Ends at https://www.prijsprofeet.be/.well-known/poppy.json.
discovery.redirects-well-known
§3
OK
poppy.json is a JSON object
The JSON document a Company publishes at /.well-known/poppy.json.
discovery.json
§2
OK
poppy.json fields have the forms section 3.1 describes
discovery.schema
§2
OK
protocol_version is the version this validator checks
protocol_version 0.3.
discovery.protocol-version
§3.1
OK
organization.domain is the host that serves poppy.json, after redirects
organization.domain www.prijsprofeet.be matches the host.
discovery.domain-matches-host
§3.1
OK
poppy.json lists at least one of agent, apis, or web
At least one of agent, apis, or web.
discovery.interface-present
§3.1
Skipped
Extension names are ones the protocol defines, or start with a domain
Not checked: poppy.json lists no extensions.
discovery.extension-names
§3.3
OK
A Company that turns off sign-in lists no way to sign in
Sign-in isn't turned off.
discovery.sign-in-disabled
§3.2
Skipped
The excluded-tasks document loads and has the fields in 9.1
Not checked: the validator checks this only in its online mode, which we do not run.
discovery.excluded-tasks
§9.1
Skipped
Each openapi or mcp reference in an alternative names an API listed in poppy.json
Not checked: the validator checks this only in its online mode, which we do not run.
discovery.alternative-references
§9.2
Sign-in server
OK
The Company has an issuer when it offers account access
Signed-out only; Session audience https://www.prijsprofeet.be.
metadata.issuer-required
§3.2
Skipped
The domain's protected resource metadata is for https://{organization.domain} and names authorization servers
Not checked: The Company has no OAuth issuer.
metadata.resource-metadata
§3.2
Skipped
auth.issuer is one of authorization_servers, and is present when there are several
Not checked: The Company has no OAuth issuer.
metadata.issuer-chosen
§3.1
Skipped
The issuer publishes OAuth Authorization Server Metadata
Not checked: The Company has no OAuth issuer.
metadata.published
§3.2
Skipped
The metadata has the fields section 3.2 requires, in the right forms
Not checked: The Company has no OAuth issuer.
metadata.schema
§3.2
Skipped
The metadata's issuer exactly matches the issuer the protected resource metadata names
Not checked: The Company has no OAuth issuer.
metadata.issuer-matches
§3.2
Skipped
protected_resources includes https://{organization.domain}
Not checked: The Company has no OAuth issuer.
metadata.protected-resources
§3.2
Skipped
The metadata has a token_endpoint
Not checked: The Company has no OAuth issuer.
metadata.token-endpoint
§3.2
Skipped
The metadata has a revocation_endpoint
Not checked: The Company has no OAuth issuer.
metadata.revocation-endpoint
§3.2
Skipped
grant_types_supported includes refresh_token
Not checked: The Company has no OAuth issuer.
metadata.grant-types
§3.2
Skipped
The metadata has an authorization_endpoint when it offers Direct Sign-In
Not checked: The Company has no OAuth issuer.
metadata.authorization-endpoint
§3.2
Skipped
The metadata has a device_authorization_endpoint when it offers Device Sign-In
Not checked: The Company has no OAuth issuer.
metadata.device-authorization-endpoint
§3.2
Skipped
scopes_supported lists every scope a sign-in can grant
Not checked: The Company has no OAuth issuer.
metadata.scopes-supported
§3.2
Skipped
Every scope in scopes_supported has a description
Not checked: The Company has no OAuth issuer.
metadata.scopes-described
§4.7
Skipped
Other Company domains select the same issuer
Not checked: The Company has no OAuth issuer.
metadata.same-issuer
§3.2
Skipped
Other domains with the same issuer have matching scope descriptions and hints
Not checked: The Company has no OAuth issuer.
metadata.same-auth
§3.2
Skipped
With Mediated Sign-In listed, the issuer's metadata lists its grant type
Not checked: The Company has no OAuth issuer.
metadata.mediated-grant
Mediated Sign-In §2
poppy.json as served
0.2 KB
{
"protocol_version": "0.3",
"organization": {
"name": "PrijsProfeet",
"domain": "www.prijsprofeet.be"
},
"apis": [
{
"type": "mcp",
"url": "https://www.prijsprofeet.be/api/v1/mcp",
"description": "Supermarket offers and shelf prices, Belgium. Read-only, no sign-in."
}
]
}
Each document is checked against the Personal Agent Protocol draft it declares in protocol_version: 0.1, 0.2 or 0.3. Section numbers refer to that draft's specification. Drafts 0.1 and 0.2 are published and frozen; draft 0.3 is in progress, and any draft can change before a stable version; see the path to 1.0.