{
 "categories": [
  "identity",
  "public-sector"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-09",
   "fact": "homepage",
   "note": "The Idura FAQ describes identity verification, signatures, and age verification, and says Idura was formerly Criipto.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "license",
   "note": "A test account is free with no credit card. Production uses a paid plan with a monthly platform fee and a per-eID usage fee.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "name",
   "note": "The FAQ says Idura was formerly Criipto and that the late-2025 rename did not change products or APIs.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.exists",
   "note": "The FAQ says Idura uses OpenID Connect and CIBA, so an application integrates with standard tools.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.kinds[0]",
   "note": "The protocol answer names OpenID Connect.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.kinds[1]",
   "note": "The Verify basics page uses the OAuth 2.0 client role and the authorization-code flow.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.kinds[2]",
   "note": "The protocol answer names CIBA beside OpenID Connect.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.auth[0]",
   "note": "A confidential application receives a client secret for a back-channel flow such as authorization code.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.auth[1]",
   "note": "The basics page recommends private-key JWT authentication for traditional web applications.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.auth[2]",
   "note": "The basics page says public clients, including the mobile example, use PKCE and do not use a client secret.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.coverage",
   "note": "Verify brokers eID login for registered applications. Production domains need a subscription, and production eID use needs a provider agreement.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.api.docs",
   "note": "Opened the Idura Verify basics on the Criipto docs host.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.sdk.exists",
   "note": "The FAQ says Idura offers dedicated SDKs and integration guides.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.sdk.official",
   "note": "The SDK answer is on Idura's own FAQ. It also lists separate Idura Signatures SDKs, which are outside this record.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "Opened a text/plain Idura file addressed to AI assistants. It is a company brief, not an API reference.",
   "source": "https://idura.eu/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "verdict.scores.api",
   "note": "OpenID Connect client registration, client secret, private-key JWT, and PKCE are documented. Production eID agreements and a paid domain remain gates.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "freshness.watch[0].url",
   "note": "Opened the Idura Verify basics.",
   "source": "https://docs.criipto.com/verify/getting-started/basics/",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "freshness.watch[1].url",
   "note": "Opened the Idura FAQ, including the Criipto rename and the protocol answer.",
   "source": "https://idura.eu/faq",
   "tier": "declared"
  },
  {
   "date": "2026-10-09",
   "fact": "freshness.watch[2].url",
   "note": "Opened the Idura assistant brief.",
   "source": "https://idura.eu/llms.txt",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-09",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://docs.criipto.com/verify/getting-started/basics/"
   },
   {
    "type": "docs",
    "url": "https://idura.eu/faq"
   },
   {
    "type": "docs",
    "url": "https://idura.eu/llms.txt"
   }
  ]
 },
 "homepage": "https://idura.eu/",
 "id": "idura-verify",
 "license": "freemium",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "client-secret",
    "private-key-jwt",
    "pkce"
   ],
   "coverage": "partial",
   "docs": "https://docs.criipto.com/verify/getting-started/basics/",
   "exists": true,
   "kinds": [
    "openid-connect",
    "oauth2",
    "ciba"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": "unknown",
   "third_party": [],
   "verdict": "unknown"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No UI probe was run. Idura Verify is an OpenID Connect broker. The end-user login still happens in the eID provider.\n",
   "ui_stack": [],
   "vendor_support": []
  },
  "sdk": {
   "exists": true,
   "languages": [],
   "official": true
  }
 },
 "name": "Idura Verify",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "signicat",
   "bankid",
   "freja-eid"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Idura",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 7,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 7,
   "rpa": null
  },
  "summary": "Idura Verify is automatable today through OpenID Connect. This record is Idura Verify, the eID broker formerly called Criipto Verify. It is not Idura Signatures, and it is not BankID, MitID, or Freja eID themselves. The FAQ says the late-2025 rename did not change products, APIs, contracts, SLAs, or pricing, and that the integration protocol is OpenID Connect and CIBA. A tenant holds applications and domains. An application receives a client ID and, for a confidential client, a client secret. The basics page also documents private-key JWT and PKCE. Test domains such as acme-corp-test.idura.broker work before a production subscription. Production domains require a paid subscription, and production eID use requires an agreement with the provider. The FAQ says a test account is free, with no credit card, and that production adds a monthly platform fee plus a per-eID usage fee. Named eIDs include MitID, Swedish BankID, Norwegian BankID, Freja eID, and the Finnish Trust Network. The FAQ says SDKs exist. This pass did not open a Verify SDK reference that separates those libraries from integration guides and from Idura Signatures SDKs. No vendor page was opened that settles whether Idura publishes an MCP server. https://idura.eu/llms.txt is a company brief for assistants. Connector catalogs were not opened. Computer-use viability is unassessed. OpenID Connect scores 7 and is the best path.\n"
 }
}