# Zywave — API Agent Score

> Score: 44/100 (Grade: F) | Domain: zywave.com | Rubric: 1.0.0 | Checked: July 30, 2026

Zywave scored 44/100 (F), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/zywave)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 44/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 42/100 (F)
- Agent Understanding: 40/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [fail] Example coverage — No README found. Investigated: sdk 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://zywave.cventevents.com/event/InsuringGrowth-Dallas/register; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [warn] Crawlable / AEO — Sitemap lastmod coverage 60% or newest entry older than 90 days. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 0%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Zywave's API contract shows meaningful strengths in crawlability but has critical gaps across schema depth, security hygiene, agent discoverability, and runnable documentation that will block partners and their AI agents from self-serving through integration. The two highest-priority areas to close are the API design surface — where missing schemas, security declarations, and examples make the contract untrustworthy for both humans and agents — and agent discoverability, where the absence of llms.txt, registry presence, and an AGENTS.md file means AI-native partners cannot find or understand your APIs without a sales conversation. Closing these gaps together will unlock self-serve partner onboarding and give AI agents the grounded, executable context they need to build correct integrations.