{
 "categories": [
  "administration",
  "public-sector"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-09-05",
   "fact": "homepage",
   "note": "Unicornis presents HyperSys as the membership register that handles join, invoices, SMS and email, annual reports from local chapters, and organisation administration.",
   "source": "https://hypersys.no/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "vendor",
   "note": "The contact page states HyperSys is made by Unicornis, a customer-owned non-profit, with organisation number NO 992 838 728 MVA.",
   "source": "https://hypersys.no/kontakt-oss/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "deployment",
   "note": "HyperSys is operated on Unicornis's own machines in Norway and is used in a browser from anywhere. That is a vendor-hosted web product.",
   "source": "https://hypersys.no/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "platforms",
   "note": "The homepage states that a browser is enough to use HyperSys.",
   "source": "https://hypersys.no/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "license",
   "note": "The page invites organisations that are not yet customers to contact Unicornis. It does not publish a public free tier.",
   "source": "https://hypersys.no/kontakt-oss/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "status",
   "note": "The functions page is a current commercial offer covering membership, dues, events, and grant modules.",
   "source": "https://hypersys.no/funksjoner-2-0/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.api.exists",
   "note": "The help article states that custom services can connect through an API coupling, and that access requires an active API agreement and API keys.",
   "source": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.api.exists",
   "note": "The functions page tells organisations to connect HyperSys to their website or use the API to build their own solutions.",
   "source": "https://hypersys.no/funksjoner-2-0/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.api.auth[0]",
   "note": "The help article requires egne API-n\u00f8klar (API keys) together with an active API agreement. No other public auth scheme is named.",
   "source": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.api.coverage",
   "note": "Named work is fetch and update of personalia, officer lists, and nightly local-chapter pages. The public page does not publish a full endpoint catalog, so coverage is partial.",
   "source": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.api.docs",
   "note": "This help article is the public API page. It points to a document attachment for the current API documentation and says the agreement is the last page of that document. The attachment is not a public endpoint catalog.",
   "source": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.api.coverage",
   "note": "The social-media article states that social-media links can be read from an organisation-information call on the HyperSys API.",
   "source": "https://hjelpe.hypersys.no/knowledge-base/sosial-medier/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "verdict.scores.api",
   "note": "The API exists and is usable for chapter and officer sync, but access is agreement-gated, support is billed, display integrations must cache about 24 hours, and the public endpoint catalog is incomplete. That is a 3\u20134 gated path; the score is 4.",
   "source": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://hypersys.no/llms.txt returned HTTP 404 on 2026-09-05.",
   "source": "https://hypersys.no/llms.txt",
   "tier": "scraped"
  },
  {
   "date": "2026-09-05",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as Unicornis's current HyperSys homepage.",
   "source": "https://hypersys.no/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the current functions page, including the not-a-CRM heading and the API mention.",
   "source": "https://hypersys.no/funksjoner-2-0/",
   "tier": "declared"
  },
  {
   "date": "2026-09-05",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current HyperSys API help article (updated 1 April 2025).",
   "source": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-09-05",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://hypersys.no/"
   },
   {
    "type": "docs",
    "url": "https://hypersys.no/funksjoner-2-0/"
   },
   {
    "type": "docs",
    "url": "https://hjelpe.hypersys.no/knowledge-base/api/"
   }
  ]
 },
 "homepage": "https://hypersys.no/",
 "id": "hypersys",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": false
  },
  "api": {
   "auth": [
    "api-key"
   ],
   "coverage": "partial",
   "docs": "https://hjelpe.hypersys.no/knowledge-base/api/",
   "exists": true,
   "kinds": []
  },
  "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 repeatable UI probe was run. Daily membership, dues, and chapter work is a browser surface. The agreement-gated API is the supported machine path. Endpoint coverage beyond the help-centre examples is not public.\n",
   "ui_stack": [
    "web-dom"
   ],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "HyperSys",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [
   "superoffice-crm"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Unicornis",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 4,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": null,
   "overall": 4,
   "rpa": null
  },
  "summary": "The best evidenced agent path into HyperSys is the vendor API on the help centre, not browser control and not a CRM connector. HyperSys is Unicornis's membership-register platform for Norwegian organisations. The functions page states it is not a CRM. API access requires an active API agreement and API keys. Unicornis bills the privacy onboarding, normally one hour, and bills API support. Callers that display data elsewhere must cache, normally about 24 hours. The help page says the API can fetch and update personalia and list officers and local chapters; a related article names an organisation-information call that can return social-media links. No public endpoint catalog, protocol list, SDK, or CLI was opened. First-party MCP ownership is not established. Computer-use viability is unassessed. This record is not SuperOffice.\n"
 }
}