Back to Assessments & Documents
Software Engineering and DevOps Active

API and Integration Lifecycle Maturity Assessment

A 56-question diagnostic across 9 domains that evaluates how APIs, events and integration flows are governed, designed, secured, run and retired, including AI agents and MCP servers as API consumers. Written for the head...

Overview

A 56-question diagnostic across 9 domains that evaluates how APIs, events and integration flows are governed, designed, secured, run and retired, including AI agents and MCP servers as API consumers. Written for the head of API and integration platform who needs to answer: are our APIs and integrations known, safe, reliable and worth what they cost?

Detailed Description

APIs and integrations now connect almost every system, partner and AI agent. When they are unknown, inconsistent or weakly protected, they become the easiest path to data loss, outages and wasted spend.

This assessment follows the order in which a dependable API and integration capability is built: a strategy and policy, an operating model, design authority and enabled teams; one inventory checked against runtime traffic, with posture and third-party risk; a design standard, specifications, schemas, contracts and versioning; governed events, reliable delivery, webhooks and integration platforms; tests and pipeline gates; gateways, authentication, authorization, limits, validation and abuse detection; safe use of APIs by AI agents and MCP servers; products, portal, onboarding and partner terms; and resilience, objectives, deprecation, migration and program value.

Questions marked (Bridge) check the link to the model that owns a neighboring practice: Enterprise Architecture, Configuration Management, DevOps Engineering, DevSecOps, Non-Human Identity and Secrets Management, Security Operations, AI Governance, Service Level Agreements and Performance, and SRE, DevOps and ITSM Convergence. Each question is scored on whether the practice is documented, implemented and effective.

Assessment Details

Audience

Head of API and integration platform, enterprise architects, CTO. Secondary: API product owners, integration engineers, API security engineers and platform teams.

Purpose

Shows where APIs and integrations are unknown, inconsistent, exposed or costly, and where AI agents reach systems without the right controls. Gives each gap a concrete next step and a measurable target.

Effort

Initial assessment: 5 to 6 hours of facilitated sessions with architecture, the platform team, provider teams, integration engineers and API security. Evidence gathering: gateway and mesh configuration and logs, inventory and discovery reports, specifications and schemas, pipeline results, integration platform records and portal analytics.

Cadence

Annually, and after a major platform change, a significant API security incident or the introduction of AI agents that call enterprise APIs.

Framework Alignment

OpenAPI Specification v3.2.1 Arazzo Specification v1.1.0 AsyncAPI Specification 3.1.0 CloudEvents Specification v1.0.2 RFC 9700 RFC 9449 RFC 9396 RFC 8705 RFC 9457 RFC 9745 RFC 8594 FAPI 2.0 Security Profile NIST SP 800-228 NIST SP 800-204A OWASP API Security Top 10 2023 OWASP Non-Human Identities Top 10 2025 OWASP Top 10 for LLM Applications 2025 OWASP Top 10 for Agentic Applications 2026 Model Context Protocol Specification 2026-07-28 MITRE ATLAS MITRE ATT&CK ISO/IEC 27001:2022 ISO/IEC 20000-1:2018 ISO/IEC/IEEE 29119-1:2022 ISO/IEC/IEEE 32675:2022 CBUAE Open Finance Regulation 2025 SAMA Open Banking Framework DAMA-DMBOK2 Revised Team Topologies 2nd Edition CNCF Platform Engineering Maturity Model DORA Capabilities Google SRE Book Google SRE Workbook FinOps Framework 2026 ITIL 4 COBIT 2019

KPIs

  • Inventory Match to Runtime - Share of APIs observed at runtime that match an inventory record. Target: 95% or higher.
  • Unplanned Breaking Changes - Breaking changes reaching consumers without a new major version per quarter. Target: 0.
  • Endpoints Behind a Gateway - Share of external and partner endpoints served through a managed gateway. Target: 100%.
  • Scoped Agent Credentials - Share of MCP servers and agent clients using scoped, delegated credentials. Target: 100%.
  • Sunsets on Date - Share of deprecated versions switched off by the published sunset date. Target: 90% or higher.

Dependencies

Enterprise Architecture (v7.9.6): enterprise standards (bridge 1.5); uses this model's API Design Standards Guide. Configuration Management (v9.9.6): CMDB links (bridge 2.5). DevOps Engineering (v1.9.6) and DevSecOps (v6.9.6): pipeline gates and security testing (bridge 5.5). Non-Human Identity and Secrets Management (v4.9.6): workload and partner client identity (bridge 6.3); Security Operations (v8.9.6): detections (bridge 6.7). AI Governance (v11.9.6): agent governance (bridge 7.3); Service Level Agreements and Performance (v5.9.6): consumer support (bridge 8.6). SRE, DevOps and ITSM Convergence (v4.9.6): objectives and tracing (bridge 9.2); IT FinOps (v5.9.6): cost allocation (9.5).

Assessment Outline

(9 domains · 56 questions)
  1. 1

    1 API and Integration Governance and Operating Model

    Strategy and policy, platform team and operating model, design authority, exceptions, alignment with enterprise architecture standards, provider enablement and the program roadmap

    • 1.1 API and Integration Strategy and Policy 1 questions
    • 1.2 Platform Team and Operating Model 1 questions
    • 1.3 Design Review Authority 1 questions
    • 1.4 Standards Exceptions 1 questions
    • 1.5 Enterprise Integration Patterns Alignment (Bridge) 1 questions
    • 1.6 Provider Enablement 1 questions
    • 1.7 Program Roadmap and Funding 1 questions
  2. 2

    2 Inventory, Discovery and Posture

    One inventory of APIs, runtime discovery of shadow and zombie APIs, integration flow inventory, security posture and data sensitivity, CMDB links and third-party API risk

    • 2.1 API Inventory and Ownership 1 questions
    • 2.2 Shadow and Zombie API Discovery 1 questions
    • 2.3 Integration Flow Inventory 1 questions
    • 2.4 API Security Posture and Data Sensitivity 1 questions
    • 2.5 Configuration Links (Bridge) 1 questions
    • 2.6 Third-Party API Risk 1 questions
  3. 3

    3 Design, Contracts and Standards

    The design standard, design-first specifications, schema registry, data contracts for integrations, versioning and compatibility, non-REST styles and machine-readable workflows

    • 3.1 API Design Standard 1 questions
    • 3.2 Design-First Specifications 1 questions
    • 3.3 Schema Registry 1 questions
    • 3.4 Data Contracts for Integrations 1 questions
    • 3.5 Versioning and Compatibility Rules 1 questions
    • 3.6 GraphQL, gRPC and Other Styles 1 questions
    • 3.7 Machine-Readable Workflows 1 questions
  4. 4

    4 Event-Driven and Enterprise Integration

    Broker and topic governance, event envelopes and descriptions, reliable delivery and dead-letter recovery, consumer lag, webhooks, integration platforms and citizen integrators, and legacy integration retirement

    • 4.1 Broker and Topic Governance 1 questions
    • 4.2 Event Envelope and Descriptions 1 questions
    • 4.3 Reliable Delivery and Dead-Letter Recovery 1 questions
    • 4.4 Consumer Lag Objectives 1 questions
    • 4.5 Webhook Security and Delivery 1 questions
    • 4.6 Integration Platforms and Citizen Integrators 1 questions
    • 4.7 Legacy Integration Retirement 1 questions
  5. 5

    5 Verification and Release Safety

    Sandboxes and mocks, specification conformance, consumer-driven contract tests, breaking-change detection and pipeline gates

    • 5.1 Sandboxes and Mocks 1 questions
    • 5.2 Specification Conformance Testing 1 questions
    • 5.3 Consumer-Driven Contract Testing 1 questions
    • 5.4 Breaking-Change Detection 1 questions
    • 5.5 Pipeline Gates (Bridge) 1 questions
  6. 6

    6 Runtime Security and Traffic Control

    Gateway coverage, consumer authentication and sender-constrained tokens, workload identity, object and function authorization, rate limits and business flow protection, input validation and abuse detection

    • 6.1 Gateway Coverage 1 questions
    • 6.2 Consumer Authentication and Token Binding 1 questions
    • 6.3 Workload and Partner Client Identity (Bridge) 1 questions
    • 6.4 Object and Function Level Authorization 1 questions
    • 6.5 Rate Limits and Business Flow Protection 1 questions
    • 6.6 Input Validation 1 questions
    • 6.7 API Abuse Detection (Bridge) 1 questions
  7. 7

    7 AI Agent and MCP Consumers

    Agent-ready API descriptions, MCP server inventory and approval, delegated agent authorization, agent traffic controls and write guardrails, tool poisoning and response injection defense, and agent traffic attribution

    • 7.1 Agent-Ready API Descriptions 1 questions
    • 7.2 MCP Server Inventory and Approval 1 questions
    • 7.3 Delegated Agent Authorization (Bridge) 1 questions
    • 7.4 Agent Write Guardrails (Bridge) 1 questions
    • 7.5 Tool Poisoning and Response Injection Defense 1 questions
    • 7.6 Agent Traffic Attribution 1 questions
  8. 8

    8 Developer Experience, Products and Monetization

    API products, the developer portal, time to first call, generated SDKs and changelogs, plans, partner onboarding and metering, and consumer support

    • 8.1 API Products 1 questions
    • 8.2 Developer Portal 1 questions
    • 8.3 Time to First Call 1 questions
    • 8.4 Generated SDKs and Changelog 1 questions
    • 8.5 Plans, Partner Onboarding and Metering 1 questions
    • 8.6 Consumer Support (Bridge) 1 questions
  9. 9

    9 Reliability, Lifecycle and Value

    Resilience patterns, reliability objectives and observability, deprecation and sunset, migration support, and program measures and value

    • 9.1 Resilience Patterns 1 questions
    • 9.2 Reliability Objectives and Observability (Bridge) 1 questions
    • 9.3 Deprecation and Sunset 1 questions
    • 9.4 Migration Support 1 questions
    • 9.5 Program Measures and Value 1 questions

At a Glance

Category Software Engineering and DevOps
Type Free
Roles 6
Domains 9
Questions 56

Still have questions? Get in touch

ITSGovernance