# Workato — API Agent Score

> Score: 56/100 (Grade: D) | Domain: workato.com | Rubric: 1.0.0 | Checked: July 24, 2026

Workato scored 56/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 57/100 (D)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 59/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples present on 3/20 pages across 2 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] Code samples in docs — Code samples present on 3/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://docs.workato.com/getting-started) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Changelog published — Newest official SDK activity 182 days ago — drifting from the contract. Investigated: sdk 50%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/workato_en, 27494 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). 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 — 3 of 50 pages have substantive content differences between markdown and HTML (avg 9% missing). Investigated: docs 83%.
- [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 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

Workato's agent discovery footprint is a genuine strength — documentation is reachable and findable without friction. However, the partner program has two critical gaps that limit how quickly partners and their AI agents can build with confidence: the API contract lacks security and governance clarity that partners need to integrate safely, and there is no executable, agent-readable layer — no runnable collections, no structured doc context, and no agent instructions file — meaning coding agents must guess at shapes, auth patterns, and workflows rather than acting on verified truth. Prioritize making the API surface trustworthy and executable first, then close the remaining context and onboarding gaps to accelerate partner time to production.