{
 "categories": [
  "identity",
  "public-sector"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-13",
   "fact": "homepage",
   "note": "Opened consumer English page presents Freja as a digital identity for login to Swedish e-services, including 1177 with Freja eID Plus, and points businesses to the business site.",
   "source": "https://frejaeid.com/en/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "vendor",
   "note": "The opened developers section brands the integrator product as Freja and directs relying parties to sales@frejaeid.se for test certificates and partner support.",
   "source": "https://org.frejaeid.com/en/developers-section/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "license",
   "note": "Production use requires a signed contract, branding assets, and a production client TLS certificate. The service is commercial for relying parties.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "deployment",
   "note": "Freja documents hosted Test and Production environments. Relying parties call Freja services; they do not install an IdP.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.exists",
   "note": "The developers section states integration methods are REST API, a Java client library, and OpenID Connect.",
   "source": "https://org.frejaeid.com/en/developers-section/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.kinds[0]",
   "note": "Authentication Service methods are HTTP POST to services.prod.frejaeid.com/authentication/1.0/initAuthentication and sibling getOneResult, getResults, and cancel endpoints.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162802/Authentication+Service",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.kinds[1]",
   "note": "The OpenID Connect general guide documents authorization-code login against Freja metadata and states that signing is not supported on OIDC.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/33423361/OpenID+Connect+-+General+Guide",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.kinds[2]",
   "note": "Production discovery lists grant_types_supported authorization_code, token_endpoint, authorization_endpoint, and userinfo_endpoint. That is OAuth 2.0 as used by OpenID Connect.",
   "source": "https://oidc.prod.frejaeid.com/oidc/.well-known/openid-configuration",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.auth[0]",
   "note": "REST access requires a client SSL/TLS certificate for Test and Production. The client certificate authenticates the relying-party application on authentication and signing requests.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.auth[1]",
   "note": "token_endpoint_auth_methods_supported includes client_secret_basic.",
   "source": "https://oidc.prod.frejaeid.com/oidc/.well-known/openid-configuration",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.auth[2]",
   "note": "token_endpoint_auth_methods_supported includes client_secret_post. The OIDC guide's token example posts client_id and client_secret in the body.",
   "source": "https://oidc.prod.frejaeid.com/oidc/.well-known/openid-configuration",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.coverage",
   "note": "Relying-party services are Authentication, Signing, and Organisation ID, plus custom identifiers. This is an IdP and signing platform, not a general application CRUD API. REST documentation version 6.0 is dated 2026-01-13.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.api.docs",
   "note": "Opened as the current Freja eID Relying Party REST API documentation index, including environments, certificates, and service list.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.sdk.exists",
   "note": "The Freja-eID/frejaeidclient README presents an official Java library for the Relying Party API, Maven coordinates com.verisec.frejaeid:FrejaEidClient:2.34.1.",
   "source": "https://raw.githubusercontent.com/Freja-eID/frejaeidclient/master/README.md",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.sdk.languages[0]",
   "note": "The repository is a Java client covering authentication, signature, custom identifier, organisation ID, and integrator management APIs.",
   "source": "https://raw.githubusercontent.com/Freja-eID/frejaeidclient/master/README.md",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.sdk.official",
   "note": "The developers section lists the Java client library and Client Library on Github next to the REST API guide.",
   "source": "https://org.frejaeid.com/en/developers-section/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.extensibility.scripting[0]",
   "note": "Relying parties send authorization-code requests, exchange the code at token_endpoint with client_id and client_secret, and read ID token or userinfo.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/33423361/OpenID+Connect+-+General+Guide",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.extensibility.scripting[1]",
   "note": "REST relying parties POST Base64 JSON initAuthRequest bodies and poll getOneResult or getResults.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162802/Authentication+Service",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.data_access.export[0]",
   "note": "The token response includes id_token. The guide states ID token validity is 1 hour.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/33423361/OpenID+Connect+-+General+Guide",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.data_access.export[1]",
   "note": "The token response includes access_token. Access token validity is 10 minutes. userinfo accepts Authorization Bearer access_token.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/33423361/OpenID+Connect+-+General+Guide",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.data_access.export[2]",
   "note": "Get One Authentication Result returns the transaction result, including requestedAttributes and a JWS payload on APPROVED.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162802/Authentication+Service",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.rpa.ui_stack[0]",
   "note": "The opened consumer product includes web login to e-services. No UI probe was run.",
   "source": "https://frejaeid.com/en/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.rpa.ui_stack[1]",
   "note": "The developers section documents the Freja mobile application, including a test mode. End-user approval is in the app.",
   "source": "https://org.frejaeid.com/en/developers-section/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "org.frejaeid.com/llms.txt opened as a Yoast-generated marketing listing, not a relying-party API or agent guide, so llms_txt is recorded as false.",
   "source": "https://org.frejaeid.com/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "verdict.scores.api",
   "note": "REST and OIDC are documented and usable in production, with an official Java client. Live use needs a contract and certificates. That is useful-with-material-limits, same band as other Nordic eID records.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Freja developers section listing REST, Java client, OpenID Connect, and Digg/Sweden Connect public-sector connection.",
   "source": "https://org.frejaeid.com/en/developers-section/",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current REST API documentation, version table through 6.0 dated 2026-01-13.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current OIDC guide, including authorization-code only and no signing.",
   "source": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/33423361/OpenID+Connect+-+General+Guide",
   "tier": "declared"
  },
  {
   "date": "2026-09-13",
   "fact": "freshness.watch[3].url",
   "note": "Opened and verified as the current production OpenID Provider metadata, including token_endpoint_auth_methods_supported.",
   "source": "https://oidc.prod.frejaeid.com/oidc/.well-known/openid-configuration",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-13",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://org.frejaeid.com/en/developers-section/"
   },
   {
    "type": "docs",
    "url": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826"
   },
   {
    "type": "docs",
    "url": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/33423361/OpenID+Connect+-+General+Guide"
   },
   {
    "type": "docs",
    "url": "https://oidc.prod.frejaeid.com/oidc/.well-known/openid-configuration"
   }
  ]
 },
 "homepage": "https://frejaeid.com/en/",
 "id": "freja-eid",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "client-tls",
    "client-secret-basic",
    "client-secret-post"
   ],
   "coverage": "partial",
   "docs": "https://frejaeid.atlassian.net/wiki/spaces/DOC/pages/2162826",
   "exists": true,
   "kinds": [
    "rest",
    "openid-connect",
    "oauth2"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "id-token",
    "access-token",
    "auth-result"
   ],
   "import": []
  },
  "extensibility": {
   "scripting": [
    "oidc-relying-party",
    "rest-relying-party"
   ],
   "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 repeatable UI probe was run. Freja eID is an eID and signing service, not a line-of-business application. The documented path is a contracted relying party calling the REST Authentication, Signature, and Organisation ID services over mutual TLS, or OpenID Connect authorization-code. OIDC does not support signing.\n",
   "ui_stack": [
    "web-dom",
    "mobile-app"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": true,
   "languages": [
    "java"
   ],
   "official": true
  }
 },
 "name": "Freja eID",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "bankid",
   "mitid",
   "id-porten",
   "feide"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Freja eID",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 6,
   "rpa": null
  },
  "summary": "Freja eID is automatable as a contracted Swedish eID and signing integration, not as BankID, MitID, ID-porten, or Feide. The consumer site presents Freja as a digital identity approved for Swedish government and EU use. Relying parties integrate through a REST Authentication Service, Signature Service, and Organisation ID Service, or through OpenID Connect. REST calls require a Freja-issued client TLS certificate and a production contract. Authentication methods include initAuthentication at services.prod.frejaeid.com/authentication/1.0/initAuthentication, plus get-one, get-many, and cancel. OpenID Connect uses authorization-code only, with discovery at oidc.prod.frejaeid.com/oidc/.well-known/openid-configuration. Token endpoint authentication is client_secret_basic or client_secret_post. Vendor documentation states OpenID Connect supports authentication, not signing. An official Java client (com.verisec.frejaeid:FrejaEidClient) wraps those REST services. Live clients are not self-service. That agreement and certificate gate is the material limit. First-party MCP ownership is not established. Computer-use viability is unassessed. API scores 6 and is the best path.\n"
 }
}