Can AI agents automate MitID?
Digitaliseringsstyrelsen · saas · identitypublic-sectorgovernment
MitID is automatable as Denmark's national digital identity, not as a self-serve relying-party API and not as BankID or ID-porten. Digitaliseringsstyrelsen states that service providers must use a certified broker; the agency does not support relying-party setup directly. The approved-broker list updated 02.07.2026 names ten brokers, including Digitaliseringsstyrelsen/NemLog-in. Public authorities that require secure login for an official task must use NemLog-in. NemLog-in documents OIOSAML 3 and 4 integration: service providers exchange SAML metadata that includes a system certificate, run an integration test, and receive assertions for MitID, MitID Erhverv, or a local IdP. Private organisations that do not perform an official task pick a commercial broker; those broker APIs are outside this record. An OIO OpenID Connect profile exists as a draft written with NemLog-in in mind; the opened NemLog-in service- provider path is OIOSAML, not a first-party MitID OIDC catalogue. First-party MCP ownership is not established. Computer-use viability is unassessed.
Best path today: api · Overall automatability: 5/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | samlsystem-certificate coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | unknown | verdict: unknown |
| Integrations | unknown | |
| CLI | unknown | |
| Extensibility | yes | certified-brokeroiosaml-relying-party webhooks: unknown |
| Data access | export: saml-assertion · import: unknown | |
| RPA / UI automation | unknown | web-dommobile-app No repeatable UI probe was run. MitID is Denmark's national eID, not a line-of-business application. Service providers must use a certified broker. The documented path is OIOSAML against NemLog-in or another approved broker, not browser control of the MitID app.
|
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | integrations | cli | rpa | computer use | overall |
|---|---|---|---|---|---|---|
| 5 | — | — | — | — | — | 5 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
homepage | declared | source | 2026-09-10 |
vendor | declared | source | 2026-09-10 |
license | declared | source | 2026-09-10 |
status | declared | source | 2026-09-10 |
modalities.api.exists | declared | source | 2026-09-10 |
modalities.api.kinds[0] | declared | source | 2026-09-10 |
modalities.api.auth[0] | declared | source | 2026-09-10 |
modalities.api.coverage | declared | source | 2026-09-10 |
modalities.api.docs | declared | source | 2026-09-10 |
modalities.extensibility.scripting[0] | declared | source | 2026-09-10 |
modalities.extensibility.scripting[1] | declared | source | 2026-09-10 |
modalities.data_access.export[0] | declared | source | 2026-09-10 |
modalities.agent_docs.llms_txt | scraped | source | 2026-09-10 |
verdict.scores.api | declared | source | 2026-09-10 |
freshness.watch[0].url | declared | source | 2026-09-10 |
freshness.watch[1].url | declared | source | 2026-09-10 |
freshness.watch[2].url | declared | source | 2026-09-10 |
freshness.watch[3].url | declared | source | 2026-09-10 |
Related tools
Other products in this database that share a category with MitID.
Last verified 2026-09-10 · volatility medium · JSON record