Smart DCC
Smart DCC (the Data Communications Company) is the Ofgem-licensed monopoly that operates Britain's national smart metering communications network, connecting electricity and gas smart meters in homes and businesses to energy suppliers, network operators and other authorised users over a single secure wide-area network. It sits in the middle of the United Kingdom energy value chain as shared infrastructure rather than as a retailer or a data marketplace, and it is regulated through the Smart Meter Communication Licence and governed by the Smart Energy Code. Its API posture reflects that position exactly. Britain mandated the infrastructure, not a consumer data right — there is no UK equivalent of the Australian Consumer Data Right for energy, so Smart DCC operates no consumer data-portability API and publishes no Green Button or Consumer Data Standards surface. The real production interface is the DCC User Interface Specification (DUIS), an XML web service reached over a DCC User Gateway Connection, plus the Self-Service Interface; the DUIS specification and its XML schema are published openly as Smart Energy Code subsidiary documents, but the gateway itself is closed to anyone who has not acceded to the Smart Energy Code and passed SMKI and User Entry Process Testing. The only self-serve, machine-readable contract Smart DCC publishes is an OpenAPI for the open-source DCC Boxed DUIS signing and validation tool on GitHub. Network statistics are shown on a public dashboard as a rendered web page with no documented open data API or bulk download, so both the consumer-data and market-data sides are effectively closed while the interface specification itself is open.
Smart DCC publishes 2 API contracts indexed on the APIs.io network: Sign API and Verify API. Tagged areas include Energy, United Kingdom, Utilities, Electricity, and Gas.
The Smart DCC catalog on APIs.io includes 1 Spectral governance ruleset.
Smart DCC’s developer surface includes engineering blog, documentation, CLI, sandbox, changelog, support, pricing, and 35 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Carbon Accounting Disclosure Standards (SBTi, PCAF, CDP, GHG Protocol) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Smart DCC Sign API
The Sign API from Smart DCC — 1 operation(s) for sign.
Smart DCC Verify API
The Verify API from Smart DCC — 1 operation(s) for verify.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
DCC Boxed DUIS Signing Tool API
OPEN COLLECTIONAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Spectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Smart DCC API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
JSON Schema 1
Standalone JSON Schema definitions for this provider's data models.
Dcc Smart Dccboxed Keystore
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 5
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 4
Authentication, authorization, and security posture
Operate 7
Status, limits, changes, and where to get help
Scroll for all 7
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
Source (apis.yml)
Smart DCC API — frequently asked questions
Does Smart DCC have an API?
Yes. APIs.io lists 2 APIs from Smart DCC, including Smart DCC Sign API and Smart DCC Verify API.
Is there an OpenAPI specification for the Smart DCC API?
Yes. APIs.io indexes 2 OpenAPI specifications for Smart DCC, each linked for download from this page.
How do I authenticate with the Smart DCC API?
Smart DCC uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Dcc Smart Authentication.
Is the Smart DCC API ready for AI agents?
Smart DCC has a Kin Score of 46.5 out of 100 (developing) and an Agent Readiness score of 29.0 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.