# Zenoti — API Agent Score

> Score: 50/100 (Grade: D) | Domain: zenoti.com | Rubric: 1.0.0 | Checked: July 29, 2026

Zenoti scored 50/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 50/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 62/100 (C)
- Developer Experience: 40/100 (F)
- Agent Discovery: 75/100 (B)
- Agent Understanding: 48/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.
- [skip] Schema coverage & depth — No surface produced evidence for this capability in this run.
- [skip] Example coverage — No surface produced evidence for this capability in this run.

### Developer Experience

- [fail] Self-service developer portal — No self-service signup detected: no signup link found on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.
- [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.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/zenoti, 3834 snippets). Investigated: docs 100%, sdk 0%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 1 failed to fetch. Investigated: docs 70%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — 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 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [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] 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

Zenoti's API program shows meaningful strengths in documentation discoverability and crawlability, but partners and their AI agents face critical friction at the most consequential moments: finding a self-serve onboarding path, understanding errors programmatically, and running real workflows against trusted examples. Closing the gaps in partner onboarding, machine-readable error handling, and runnable API context should be the immediate priority — these are the barriers that prevent partners from reaching value independently and that block AI agents from integrating correctly without human intervention.