AI Readiness Audit
Ref. APM-B33239F3 · Confidential

Constant Contact API v3

An independent assessment of whether the Constant Contact API v3 specification is ready for AI-assisted integration and autonomous agents, prepared for Constant Contact.

Prepared for
Constant Contact
Subject
Constant Contact API v3 v1.0.221
Scope
111 operations · 4 pillars · 3 groups
Date
October 2026
53/100
Not ready
Functional for AI-assisted builds.
Partially ready for autonomous agents.
Reach AI-ready by Phase 1; resolve all findings → 100 · AI-ready
Import blocked: SDK, docs, and MCP generators will refuse this spec

The validation engine found 1 blocking violation: YAML data is invalid.. Import tools reject the specification outright until it is fixed, so nothing downstream can be generated regardless of the other pillar scores. While this gate is open, the Standards Compliance score is capped at 40 and every AI pillar weights standards at 60% (normally 30%). Fixing the blocker in Phase 1 lifts the caps; the score projection below shows what that unlocks.

1
Critical blocker stopping entire operation groups for agents
1112
Total instances: 1 critical, 10 high, 116 medium, 985 low
27
Rule groups across 4 pillars: 1 critical, 10 high sev. instances
Executive summary

Your API cannot generate SDKs, documentation, or MCPs due to one blocking violation that must be resolved first. The overall composite score of 53.2 indicates that your API is not ready, with significant weaknesses in standards compliance at 40 and documentation readiness at 61.2. While the API is functional for AI-assisted builds, it is only partially ready for autonomous agents, as evidenced by 27 rule groups and 1112 instances of findings. Addressing the blocking violation is the most critical action to improve your API's readiness.

Readiness by pillar
Not ready 53 / 100
FoundationThe spec itself
40/100
Standards Compliance
OpenAPI validity, structural correctness, specification conformance, and import linting: can machines trust your spec?
40Not ready
Build Time ReadinessAI writes the code
62/100
Documentation Readiness for AI
Descriptions that say when to use an operation, examples that pin down every shape: whether an AI can learn the truth of your API from what you publish
61Significant gaps
SDK Readiness for AI
Clean types, predictable naming, correct formats: whether production-grade client code can be generated from your spec, by SDK pipelines and AI coding assistants alike
63Significant gaps
Runtime ReadinessAgents make the calls
55/100
MCP Readiness
Whether your operations survive being turned into tools: distinct names, descriptions that carry what an agent must know, safe invocation semantics, auth, error recovery, and context budget
55Significant gaps
Score projection · what fixing each phase unlocks
Todaycurrent score
53
Not ready
Phase 1fix criticals
99
AI-ready
Phase 2+ fix highs
99
AI-ready
Phase 3+ fix mediums & lows
100
AI-ready
About this report. We evaluated the Constant Contact API v3 specification against thousands of deterministic rules we have refined over twelve years of building API tooling, supplemented by AI-based analysis. Every finding is reproducible from the spec itself, scored consistently, and paired with a concrete fix.
What's at stake

Where you’re exposed – and where you’re not

4 failure modes across 3 groups. Some are active risks; others are under control.

Foundation The spec itself 40 / 100
Active risk · Standards compliance
YAML Data Violations Disrupt Integrations
The invalid YAML data breaks toolchains and SDK generation, preventing downstream integrations from functioning correctly.
22→29
code quality score out of 40: the lift consumers achieve when the underlying spec is clean and standards-compliant
APIMatic Context Plugins research · Series B · June 2026
Build Time Readiness AI writes the code 62 / 100
Elevated risk · Documentation readiness for AI
AI readers misinterpret API due to gaps
Sparse and generic documentation leads to incorrect assumptions, risking effective integration with the Constant Contact API.
74%
of developers name missing or unclear documentation as the top reason they abandon an API. AI readers are stricter: what a human would ask about, an AI assumes.
APIMatic Developer Experience research · June 2026
Elevated risk · SDK readiness for AI
SDKs generate incorrect types and formats
The success response for 2xx codes lacks a body schema, causing integration code to misinterpret data structures.
0
fabricated API constructs when a coding assistant was grounded in an AI-ready spec. Ambiguity in the spec is what triggers hallucinated integration code
APIMatic Context Plugins research · 6 APIs · 3 models · June 2026
Runtime Readiness Agents make the calls 55 / 100
Elevated risk · MCP readiness
Autonomous agents struggle with API execution
The Constant Contact API has confusable operations and lacks JSON media types, which disrupts agent performance.
65%
reduction in token consumption when agent tools are grounded in authoritative API context. Bloated or confusable tools consume up to 3.3× more.
APIMatic Context Plugins research · Series A · June 2026
The evidence numbers come from our controlled research: 6 experiments across 3 models, 6 commercial APIs, and 3 languages. We derive each card's risk status from this API's pillar scores. Full methodology at apimatic.io.
Contents

What's inside the full report

Unlock the full report

Book a free call to view the full report and the roadmap our team recommends to upgrade your developer and agentic experience.

Book a free call to view the full report