Register your Peppol Participant Identifier (ISO 6523 scheme + value, e.g., 0088:GLN) with your certified access point provider, which registers it in the SML
Confirm the SMP record by querying the SML DNS: resolve b-{MD5(participant-id)}.iso6523-actorid-upis.acc.edelivery.tech.ec.europa.eu
Retrieve the SMP service metadata endpoint from the DNS response and GET /{participantId}/services/{documentTypeId} to confirm supported document types
Obtain the recipient's Peppol PKI certificate from the SMP endpoint metadata and verify it chains to the Peppol PKI root
Send a test AS4 message to the OpenPeppol conformance endpoint, confirming signed and encrypted payload delivery via HTTPS
Known gotchas
SML and SMP are separate layers; SML is the central DNS directory (operated by OpenPeppol) while SMPs are per-access-point — do not confuse the two
Access points must hold valid Peppol PKI production certificates; test certificates are not accepted on the live network
AS4 requires two-way signed and encrypted messaging with ebMS3 headers; a plain HTTPS POST to the endpoint will be rejected
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp