Iec Cim

IEC Common Information Model (CIM) is an international standard developed by the International Electrotechnical Commission for representing electrical power system data and facilitating data exchange between applications.

Iec Cim publishes 7 API contracts indexed on the APIs.io network, including iec-cim Customers API, iec-cim Metering API, iec-cim Network Assets API, and 4 more. Tagged areas include Energy, Utilities, and Metering.

The Iec Cim catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Iec Cim’s developer surface includes authentication and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

29.5/100 thin ▬ flat Agent 26/100 agent aware Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve

1 published contract

Energy Utilities Metering

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Customer Relationship Management

BC-420

Customers

GET /customers

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 29.5/100 · thin

Contract Quality 11.7 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 1.1 / 17

Operational Transparency 0.8 / 11

Contract Governance 1.0 / 10

Discoverability 4.4 / 9

Regulatory Posture 3.5 / 15

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/iec-cim/"><img src="https://apis.io/badge/iec-cim/card.svg" alt="Iec Cim on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 6.4 — up to +18.7 composite points Ask about this →
Developer Ergonomics scores 28.6 — up to +14.3 composite points Ask about this →
Operational Transparency scores 7.1 — up to +12.1 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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 the provider profile at artifacts.apis.io/iec-cim/apis.yml: open an issue on github.com/api-evangelist/iec-cim to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

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.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 7

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

IEC CIM 61970 Energy Management API

The IEC CIM 61970 standard defines the Common Information Model for energy management systems (EMS), enabling data exchange for power system network models, measurements, and to...

IEC CIM AMI Smart Meter API

The IEC CIM AMI (Advanced Metering Infrastructure) APIs from AMI head-end systems provide smart meter readings, interval data, usage points, and demand response signals using CI...

iec-cim Customers API

Customer service agreements and locations

iec-cim Metering API

Meters and interval readings (IEC 61968-9 AMI)

iec-cim Network Assets API

Distribution network equipment – transformers, switches, lines, conductors

iec-cim Outages API

Outage events and management

iec-cim Work Orders API

Maintenance and construction work orders

Scroll for all 7

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

IEC CIM 61968 Distribution Management API

OPEN COLLECTION

IEC CIM 61968 Distribution Management Customers API

OPEN COLLECTION

IEC CIM 61968 Distribution Management Customers Metering API

OPEN COLLECTION

IEC CIM 61968 Distribution Management Customers Network Assets API

OPEN COLLECTION

IEC CIM 61968 Distribution Management Customers Outages API

OPEN COLLECTION

IEC CIM 61968 Distribution Management Customers Work Orders API

OPEN COLLECTION

Iec Cim API pricing

Not yet checked against Iec Cim's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Iec Cim's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Iec Cim Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Iec Cim Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Iec Cim Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Iec Cim Context

20 classes · 18 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Iec Cim — jsonschema rules

5 rules · 3 warn-severity 2 info-severity

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

IEC CIM Asset

15 properties

JSON SCHEMA

Security Posture 2

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

Iec Cim Authentication

http/oauth2 · 2 schemes

SECURITY

Iec Cim Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Iec Cim Scopes

2 scopes · clientCredentials

2 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Iec Cim Agentic Access

8 operations

8 operations · 0 acting

AGENTIC

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

name: Iec Cim
aid: iec-cim
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
specificationVersion: '0.23'
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  try_now_blocked_by: example-domain
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/iec-cim.png
url: https://raw.githubusercontent.com/api-evangelist/iec-cim/refs/heads/main/apis.yml
apis:
- aid: iec-cim:iec-cim-61970-ems-api
  name: IEC CIM 61970 Energy Management API
  tags:
  - CIM
  - EMS
  - Energy
  - Transmission
  - Utilities
  - XML
  humanURL: https://www.iec.ch/
  baseURL: https://ems-gateway.utility.example.com/cim/61970
  properties:
  - url: https://www.iec.ch/
    type: Documentation
  - url: https://cimug.ucaiug.org/
    type: Reference
  description: The IEC CIM 61970 standard defines the Common Information Model for energy management systems (EMS), enabling
    data exchange for power system network models, measurements, and topology across transmission utility systems.
- aid: iec-cim:iec-cim-ami-smart-meter-api
  name: IEC CIM AMI Smart Meter API
  tags:
  - AMI
  - CIM
  - Energy
  - Metering
  - Smart Meter
  - Utilities
  - XML
  humanURL: https://www.iec.ch/
  baseURL: https://ami-gateway.utility.example.com/cim
  properties:
  - url: https://www.iec.ch/
    type: Documentation
  - url: https://cimug.ucaiug.org/
    type: Reference
  description: The IEC CIM AMI (Advanced Metering Infrastructure) APIs from AMI head-end systems provide smart meter readings,
    interval data, usage points, and demand response signals using CIM XML data models compliant with IEC 61968-9 for utility
    grid operations.
- aid: iec-cim:iec-cim-customers-api
  name: iec-cim Customers API
  description: Customer service agreements and locations
  humanURL: https://www.iec.ch/
  baseURL: https://ami-gateway.utility.example.com/cim/61968
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/iec-cim-customers-api-openapi.yml
  - type: Documentation
    url: https://www.iec.ch/
  - type: Reference
    url: https://cimug.ucaiug.org/
- aid: iec-cim:iec-cim-metering-api
  name: iec-cim Metering API
  description: Meters and interval readings (IEC 61968-9 AMI)
  humanURL: https://www.iec.ch/
  baseURL: https://ami-gateway.utility.example.com/cim/61968
  tags:
  - Metering
  properties:
  - type: OpenAPI
    url: openapi/iec-cim-metering-api-openapi.yml
  - type: Documentation
    url: https://www.iec.ch/
  - type: Reference
    url: https://cimug.ucaiug.org/
- aid: iec-cim:iec-cim-network-assets-api
  name: iec-cim Network Assets API
  description: Distribution network equipment – transformers, switches, lines, conductors
  humanURL: https://www.iec.ch/
  baseURL: https://ami-gateway.utility.example.com/cim/61968
  tags:
  - Network Assets
  properties:
  - type: OpenAPI
    url: openapi/iec-cim-network-assets-api-openapi.yml
  - type: Documentation
    url: https://www.iec.ch/
  - type: Reference
    url: https://cimug.ucaiug.org/
- aid: iec-cim:iec-cim-outages-api
  name: iec-cim Outages API
  description: Outage events and management
  humanURL: https://www.iec.ch/
  baseURL: https://ami-gateway.utility.example.com/cim/61968
  tags:
  - Outages
  properties:
  - type: OpenAPI
    url: openapi/iec-cim-outages-api-openapi.yml
  - type: Documentation
    url: https://www.iec.ch/
  - type: Reference
    url: https://cimug.ucaiug.org/
- aid: iec-cim:iec-cim-work-orders-api
  name: iec-cim Work Orders API
  description: Maintenance and construction work orders
  humanURL: https://www.iec.ch/
  baseURL: https://ami-gateway.utility.example.com/cim/61968
  tags:
  - Work Orders
  properties:
  - type: OpenAPI
    url: openapi/iec-cim-work-orders-api-openapi.yml
  - type: Documentation
    url: https://www.iec.ch/
  - type: Reference
    url: https://cimug.ucaiug.org/
common:
- type: Plans
  url: plans/iec-cim-plans-pricing.yml
- type: RateLimits
  url: rate-limits/iec-cim-rate-limits.yml
- type: FinOps
  url: finops/iec-cim-finops.yml
- type: CapabilityMap
  url: capabilities/iec-cim-capability-edges.yml
  name: Iec Cim Business Capability Map
- type: Website
  url: https://iec.ch
- type: AgenticAccess
  url: agentic-access/iec-cim-agentic-access.yml
- type: DomainSecurity
  url: security/iec-cim-domain-security.yml
- type: Authentication
  url: authentication/iec-cim-authentication.yml
- type: OAuthScopes
  url: scopes/iec-cim-scopes.yml
- aid
- name
- description
- image
- tags
- properties
maintainer:
  name: Kin Lane
  email: kin@apievangelist.com
modified: '2026-09-16'
description: IEC Common Information Model (CIM) is an international standard developed by the International Electrotechnical
  Commission for representing electrical power system data and facilitating data exchange between applications.
tags:
- Energy
- Utilities
- Metering

Iec Cim API — frequently asked questions

Does Iec Cim have an API?

Yes. APIs.io lists 7 APIs from Iec Cim, including IEC CIM 61970 Energy Management API, IEC CIM AMI Smart Meter API and iec-cim Customers API, and 4 more.

Is there an OpenAPI specification for the Iec Cim API?

Yes. APIs.io indexes 5 OpenAPI specifications for Iec Cim, each linked for download from this page.

How do I authenticate with the Iec Cim API?

Iec Cim documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Iec Cim Authentication.

How much does the Iec Cim API cost?

APIs.io lists 3 pricing plans for Iec Cim, with each plan's price, limits and inclusions under Pricing on this page.

Is the Iec Cim API ready for AI agents?

Iec Cim has a Kin Score of 29.5 out of 100 (thin) and an Agent Readiness score of 25.9 (agent-aware), scored by API Evangelist on 2026-11-13.

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/iec-cim"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/iec-cim/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/iec-cim/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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