Kraken Technologies website screenshot

Kraken Technologies

Kraken Technologies is the United Kingdom energy technology company behind Kraken, the licensed cloud operating system for utilities. Founded in 2016 inside Octopus Energy and spun out as an independent business, Kraken says it supports more than 90 million customer accounts for licensees including E.ON Next, EDF, Origin, Tokyo Gas, National Grid, Good Energy, Plenitude, Energy Queensland, Essential Energy, Portsmouth Water and TalkTalk across electricity, gas, water and broadband. It sits one layer behind the utility rather than in front of the consumer: it does not hold a supply licence, does not settle in the wholesale market and does not publish grid or market data, so the retailers and networks it powers carry the regulatory obligations, not Kraken. Its API posture matches that position and is honestly closed. The Open Kraken programme publicly advertises APIs, events, embedded apps, Flow automation and an MCP-based AI access layer, but every reference surface is gated: docs.kraken.tech forces SSO login on every path, no base URL or endpoint is published anywhere, the Tako design-system package requires a private npm token issued by email, and the Marketplace runs under signed access-and-use terms. There is no self-serve developer signup, no consumer data-portability API of its own, and no open market data.

Kraken Technologies publishes 2 APIs on the APIs.io network. Tagged areas include Energy, United Kingdom, Utilities, Electricity, and Gas.

Kraken Technologies’ developer surface includes authentication, changelog, documentation, SDKs, engineering blog, support, legal docs, and 27 more developer resources.

29.8/100 thin ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
2 APIs 1 MCP Servers
EnergyUnited KingdomUtilitiesElectricityGasSmart MeteringDemand ResponseDERBillingEnergy Platform

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/kraken-technologies: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Open Kraken APIs and Events

Open Kraken is the integration layer of the Kraken utility operating system. Kraken publicly describes it as "APIs, events and MCP" for building apps and experiences against dat...

Open Kraken AI Access Layer (MCP)

An AI access layer that Kraken announced as an expansion of Open Kraken, built using the Model Context Protocol and described as MCP gateways that let a utility's own AI agents ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Kraken Technologies Authentication

jwt-bearer/saml/sso · 3 schemes

SECURITY

Kraken Technologies Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Kraken Technologies Vulnerability Disclosure

Hackerone · contact published

SECURITY

Kraken Technologies Trust Center

ISO/IEC 27001:2022, SOC 1 Type 2, SOC 2 Type 2

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 8

Authentication, authorization, and security posture

Scroll for all 8

Operate 4

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: kraken-technologies
url: https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/apis.yml
name: Kraken Technologies
kind: company
description: 'Kraken Technologies is the United Kingdom energy technology company behind Kraken, the licensed cloud operating
  system for utilities. Founded in 2016 inside Octopus Energy and spun out as an independent business, Kraken says it supports
  more than 90 million customer accounts for licensees including E.ON Next, EDF, Origin, Tokyo Gas, National Grid, Good Energy,
  Plenitude, Energy Queensland, Essential Energy, Portsmouth Water and TalkTalk across electricity, gas, water and broadband.
  It sits one layer behind the utility rather than in front of the consumer: it does not hold a supply licence, does not settle
  in the wholesale market and does not publish grid or market data, so the retailers and networks it powers carry the regulatory
  obligations, not Kraken. Its API posture matches that position and is honestly closed. The Open Kraken programme publicly
  advertises APIs, events, embedded apps, Flow automation and an MCP-based AI access layer, but every reference surface is
  gated: docs.kraken.tech forces SSO login on every path, no base URL or endpoint is published anywhere, the Tako design-system
  package requires a private npm token issued by email, and the Marketplace runs under signed access-and-use terms. There
  is no self-serve developer signup, no consumer data-portability API of its own, and no open market data.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://www.kraken.tech/favicon-96x96.png
tags:
- Energy
- United Kingdom
- Utilities
- Electricity
- Gas
- Smart Metering
- Demand Response
- DER
- Billing
- Energy Platform
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: kraken-technologies:open-kraken-apis-and-events
  name: Open Kraken APIs and Events
  description: Open Kraken is the integration layer of the Kraken utility operating system. Kraken publicly describes it as
    "APIs, events and MCP" for building apps and experiences against data and capabilities inside Kraken and for bringing
    data in from a licensee's own apps and third-party tools, alongside the Flow drag-and-drop automation tool and Embedded
    Apps that render inside the Kraken agent desktop. No base URL, endpoint list, authentication scheme or machine-readable
    contract is published anywhere on the public web. The reference documentation at docs.kraken.tech returns an SSO login
    wall on every path probed on 2026-07-27, including /openapi.json, /llms.txt and /.well-known/openid-configuration, each
    of which redirects to /auth/login/ and serves text/html rather than a spec. Access is available only to Kraken licensees
    and contracted partners.
  humanURL: https://www.kraken.tech/open-kraken
  tags:
  - Energy
  - Utilities
  - Integration
  - Event
  - Embedded Apps
  tags_raw:
  - Energy
  - Utilities
  - Integration
  - Events
  - Embedded Apps
  properties:
  - type: Documentation
    url: https://www.kraken.tech/open-kraken
  - type: Documentation
    url: https://docs.kraken.tech/
  - type: ChangeLog
    url: https://www.kraken.tech/product-updates
  - type: Authentication
    url: authentication/kraken-technologies-authentication.yml
  - type: Conventions
    url: conventions/kraken-technologies-conventions.yml
  - type: SourceCode
    url: https://github.com/kraken-tech/kraken-apps-examples
- aid: kraken-technologies:open-kraken-ai-access-layer-mcp
  name: Open Kraken AI Access Layer (MCP)
  description: An AI access layer that Kraken announced as an expansion of Open Kraken, built using the Model Context Protocol
    and described as MCP gateways that let a utility's own AI agents orchestrate approved actions across Kraken, with fair
    use included. Kraken states the layer is being gradually released. No MCP server URL, tool list, scope model or transport
    is published; a probe of mcp.kraken.tech on 2026-07-27 did not resolve. MCP is the only protocol Kraken names for this
    surface, and it is an agent-integration protocol rather than an energy data standard.
  humanURL: https://www.kraken.tech/open-kraken
  tags:
  - Energy
  - MCP
  - AI Agents
  - Utilities
  properties:
  - type: Documentation
    url: https://www.kraken.tech/open-kraken
  - type: Announcement
    url: https://www.kraken.tech/press-releases/kraken-expands-open-kraken-with-ai-access-layer-and-marketplace
  - type: Documentation
    url: https://docs.kraken.tech/
  - type: MCPServer
    url: mcp/kraken-technologies-mcp.yml
common:
- type: DomainSecurity
  url: security/kraken-technologies-domain-security.yml
- type: Authentication
  url: authentication/kraken-technologies-authentication.yml
- type: Conventions
  url: conventions/kraken-technologies-conventions.yml
- type: Components
  url: components/kraken-technologies-components.yml
- type: Packages
  url: packages/kraken-technologies-packages.yml
- type: MCPServer
  url: mcp/kraken-technologies-mcp.yml
- type: LLMsTxt
  url: llms/kraken-technologies-llms.txt
- type: Conformance
  url: conformance/kraken-technologies-conformance.yml
- type: Compliance
  url: https://www.kraken.tech/legal/trust-center
- type: Lifecycle
  url: lifecycle/kraken-technologies-lifecycle.yml
- type: ChangeLog
  url: changelog/kraken-technologies-changelog.yml
- type: Security
  url: https://www.kraken.tech/vulnerability-disclosure-process
- type: Website
  url: https://www.kraken.tech/
- type: Documentation
  url: https://docs.kraken.tech/
- type: DesignSystem
  url: https://tako.kraken.tech/
- type: SDK
  url: https://github.com/kraken-tech/kraken-apps-examples
- type: GitHubOrganization
  url: https://github.com/kraken-tech
- type: GitHubOrganization
  url: https://github.com/octoenergy
- type: LinkedIn
  url: https://www.linkedin.com/company/krakentech/
- type: Blog
  url: https://www.kraken.tech/insights
- type: PressReleases
  url: https://www.kraken.tech/press-releases
- type: ChangeLog
  url: https://www.kraken.tech/product-updates
- type: Partners
  url: https://www.kraken.tech/marketplace
- type: PartnerProgram
  url: https://www.kraken.tech/bpo-partner-program
- type: VulnerabilityDisclosure
  url: https://www.kraken.tech/vulnerability-disclosure-process
- type: VulnerabilityDisclosure
  url: security/kraken-technologies-vulnerability-disclosure.yml
- type: TrustCenter
  url: https://www.kraken.tech/legal/trust-center
- type: TrustCenter
  url: security/kraken-technologies-trust-center.yml
- type: Support
  url: https://support.kraken.tech/
- type: Legal
  url: https://www.kraken.tech/legal
- type: Subprocessors
  url: https://www.kraken.tech/legal/subprocessors
- type: DataProcessingAgreement
  url: https://www.kraken.tech/legal/dpa
- type: TermsOfService
  url: https://www.kraken.tech/legal/marketplace-access-and-use-terms
- type: PrivacyPolicy
  url: https://www.kraken.tech/legal/privacy-notice
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/kraken-technologies"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/kraken-technologies/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/kraken-technologies/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.