# Middesk — API Agent Score

> Score: 63/100 (Grade: C) | Domain: middesk.com | Rubric: 1.0.0 | Checked: July 24, 2026

Middesk scored 63/100 (C), classified "partially-ready".

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

## Summary

- Overall: 63/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 61/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples present on 2/16 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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://www.middesk.com/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://docs.middesk.com/quickstart with a runnable first-call sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 2/16 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [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

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/middesk, 1757 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 0/1 sitemap doc pages (0%); 1 missing. Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 2 of 4 endpoints have aggressive caching or missing cache headers. Investigated: docs 90%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 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] Description consistency across surfaces — Only 1 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

Middesk's API program has a strong foundation in documentation discovery, but two areas put partner and agent adoption at risk: agent usability and agent understanding. There is no runnable, test-backed collection for partners or their AI agents to build against, and the program lacks the structured context (agent instruction files, machine-readable doc metadata) that modern coding agents require to integrate correctly without guessing. Prioritize making the API executable and agent-legible first, then close the remaining security hygiene gap to give enterprise partners the governance confidence they need to commit to the integration.