CMS Energy · Agentic Access

CMS Energy Agentic Access

x-agentic-access generated

CMS Energy exposes 8 API operations that an AI agent could call, of which 1 are state-changing ‘acting’ operations. This is a recommended x-agentic-access execution contract — the scope, audience, consequence tier, short-lived token constraints, and escalation each action should carry before it is handed to an autonomous agent.

By consequence: 7 read and 1 safety-critical.

1 operation are classed safety-critical and should require human-in-the-loop approval at runtime.

Contracts are classified heuristically from the provider’s OpenAPI and refresh on every APIs.io network build; audience is bound per deployment. The model follows Curity’s Access Intelligence (apidays Munich 2026). Browse every provider’s agent contracts at agentic-access.apis.io.

ElectricEnergyGreen ButtonMichiganNatural GasUtilityFortune 500

Operations: 8 Acting: 1 Human-in-the-loop: 1 Method: generated

By consequence

read 7 safety-critical 1

Highest-consequence actions

The physical and safety-critical operations an agent could invoke — the ones that most warrant scoped tokens, tight TTLs, and escalation. Full per-operation contracts are in the source below.

Method	Path	Consequence	Human-in-loop
DELETE	/authorizations/{id}	safety-critical	required

Source

Agentic Access

generated: '2026-07-15'
method: generated
source: openapi/cms-energy-openapi.yml
description: Recommended x-agentic-access execution contracts, classified heuristically from
  the OpenAPI. A governance starting point for exposing this API to AI agents — review and bind
  audience per deployment. See research/curity/agentic-governance/.
summary:
  operations: 8
  by_action_class:
    connected: 7
    acting: 1
  by_consequence:
    read: 7
    safety-critical: 1
  human_in_the_loop_required: 1
operations:
- path: /authorizations
  method: get
  operationId: listAuthorizations
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /authorizations/{id}
  method: get
  operationId: getAuthorization
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /authorizations/{id}
  method: delete
  operationId: deleteAuthorization
  x-agentic-access:
    action-class: acting
    consequence: safety-critical
    subject: required
    audience: null
    token:
      max-ttl: 120
      exchange: true
      purpose-required: true
      proof-of-possession: true
    escalation:
      human-in-the-loop: required
    audit: required
- path: /meters
  method: get
  operationId: listMeters
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /meters/{id}
  method: get
  operationId: getMeter
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /bills
  method: get
  operationId: listBills
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /intervals
  method: get
  operationId: listIntervals
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
- path: /DataCustodian/espi/1_1/resource/Batch/Subscription/{subscriptionId}/UsagePoint/{usagePointId}
  method: get
  operationId: getEspiBatch
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none