Can AI agents automate Digital Post?

Digital Post is automatable as Digitaliseringsstyrelsen's Danish national mailbox platform (NgDP), not as e-Boks, mit.dk, Digipost, or Norwegian Digital Post til Innbyggere. Those clients draw on the same store for authority mail; private-company mail stays on the sender's chosen client. The best path is the published REST interfaces. Recipients use REST PUSH, REST PULL, or REST PUBLISH/SUBSCRIBE. Senders use REST PUSH, REST PULL, SFTP, or REST PUSH mass-send. Single messages are XML; mass sends use tar.lzma. Target delivery is about 20 seconds for single REST sends and within 24 hours for mass and SFTP. Production REST is at https://api.digitalpost.dk. Callers must present an OCES organisation or system certificate for mutual TLS and send the system's authenticationToken as Authorization Basic (system id as username, API key as password). The system must be active in Administrativ Adgang and belong to the same CVR as the certificate; the caller IP must match the registered range. Public authorities must attach at least one sender system and one recipient system before they can exchange Digital Post. First-party MCP ownership is not established. Official SDKs, a product CLI, and iPaaS catalogs were not established. Computer-use viability is unassessed. API scores 5 because the REST contract is documented production machinery with material registration, certificate, and IP-allowlist gates.

Best path today: api · Overall automatability: 5/10