{
  "id": "p_WKKbEDy1uUoPfYtl",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_WKKbEDy1uUoPfYtl",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You have a product demo on Friday. It pulls energy tariffs and account data into an app, and you have been told to pick a retailer whose API you can try this afternoon. Two names are on your list: Origin Energy in Australia and EDF Energy in Great Britain. Each sells gas and electricity to around five million customer accounts. Both run their retail business on Kraken, the platform licensed from Octopus Energy Group. On paper they look like twins.\n\nThe APIs.io catalog scores them close together. On the Gas tag, Origin gets 64.8 and EDF gets 62.7 on the Kin Score, a gap of 2.1 points. The post is careful about what that number means: it measures the public API surface, not the company or the quality of its energy supply.\n\nThe post also admits a slip in its own ranking. EDF is third on the tag page, not second. The provider in second place is AEMO, the Australian market operator. The catalog's tooling skipped it as \"same company as Origin\" because both sit on Australian domains. The post calls that a heuristic error. It also says AEMO runs the market and does not sell gas, so Origin against EDF is the comparison a buyer would actually make.\n\nThat 2.1-point gap hides a sharp split. Origin is a designated data holder under Australia's Consumer Data Right, and it implements that properly. It is on the CDR Register and serves the Consumer Data Standards discovery endpoints anonymously. Its mTLS endpoint is certified by the ACCC's own certificate authority. But the customer data behind all that is reachable only by an accredited data recipient acting with a consumer's consent. Its Kraken partner portal can be read in public but not used self-serve. The record lists access as gated, approval onboarding.\n\nBritain has no consumer data-portability right, so nothing requires EDF to publish anything. It publishes anyway. Its Kraken developer portal is fully public and onboarding is open. The products endpoint returned 21 live EDF products without a key. Neither company lists a price for API access.\n\nThe surfaces are mostly the same Kraken modules: account import, orders, quotes, voice and external events. Origin has 25 API pages, 22 OpenAPI files, one AsyncAPI, 39 JSON Schemas and 95 artifact pointers. EDF has 16 API pages, 15 OpenAPI files, one GraphQL schema and 32 pointers. Origin adds CDR data-holder APIs for electricity usage, account billing and distributed energy resources. EDF has a GraphQL API anyone can introspect without an account, plus a Products API with 10 operations. Only 59.1% of Origin's contracts are callable as published, against 100.0% of EDF's.\n\nFacet by facet, Origin wins three and EDF wins three. Origin takes contract governance 80.9 to 18.2, operational transparency 84.2 to 57.9 and contract quality 70.7 to 53.9. EDF takes access clarity 44.7 to 0.0, developer ergonomics 66.1 to 51.8 and discoverability 79.5 to 78.6. Origin's zero on access clarity is what an accreditation-only front door scores, however well the documentation behind it is written.\n\nOn agent readiness the ranking flips. Origin scores 40.5 and is recorded as agent-ready. EDF scores 38.7 and is recorded as agent-native, because that band is gated on specific safety and contract checks rather than read off the score. Neither has an MCP server, an agent card, protected resource metadata or a consent-identity mechanism. The agent skills and agentic-access profiles on both sides were derived by the catalog, so neither company gets credit for them.\n\nSo for your Friday demo, the answer is plain. If you are an accredited CDR data recipient in Australia, or a Kraken partner with an Origin agreement, Origin offers the deeper surface: more contracts, better governance around them, and regulated usage and billing data. If you want to call a retailer's API this afternoon, EDF is the only one of the two that lets you, with open onboarding, anonymous tariff data and every contract callable.\n\nWhat you take away is that the composite rewards Origin for paperwork and EDF for opening the door, and the 2.1-point gap understates how different the two are to use. The post also shows where each could move. EDF could close its governance gap with versioning, change history and lifecycle signals. Origin cannot move its access-clarity zero while accreditation is the only way in, though a sandbox or an open plan-data endpoint on its own host would score.\n\nRead the original: https://apis.io/2026/11/03/origin-energy-vs-edf-energy-same-kraken-platform-opposite-front-doors/",
  "title": "You Need an Energy Retailer's API Today. Origin and EDF Both Run Kraken, but Only One Lets You In",
  "topics": [
    "energy-apis",
    "kin-score",
    "api-access",
    "agent-readiness"
  ],
  "published_at": "2026-11-03T19:03:20.324Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}