# MuleSoft — API Agent Score

> Score: 83/100 (Grade: A) | Domain: mulesoft.com | Rubric: 1.0.0 | Checked: September 4, 2026

MuleSoft scored 83/100 (A), classified "ai-ready".

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

## Summary

- Overall: 83/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 92/100 (A+)
- Developer Experience: 75/100 (B)
- Agent Discovery: 96/100 (A+)
- Agent Understanding: 84/100 (A)
- Agent Usability: 69/100 (C)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication is documented on the docs site at https://docs.mulesoft.com/connectors-home/llms.txt, even though it isn't declared in the API spec. Investigated: docs 100%, spec 50%, wellknown 0%.
- [warn] Machine-readable, versioned contract — The API sets a version ("1.0.0") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 98%, docs 95%.
- [warn] Schema coverage & depth — 15 of 73 public signatures use loose types (anyTypeRatio=0.205). Investigated: sdk 75%, spec 52%.
- [warn] Security & governance hygiene — Moderate footprint: 14 direct dependencies. Investigated: sdk 83%, spec 80%, wellknown 0%.
- [pass] Example coverage — Only 20% of parameters and responses (135 of 681) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, sdk 50%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://anypoint.mulesoft.com/login/ (client-rendered, so its contents couldn't be classified); free tier or sandbox is documented in pricing/docs. Investigated: docs 100%.
- [pass] Description completeness — Only 34% of operations and parameters have descriptions (132 of 215 ops, 15 of 233 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 0%.
- [pass] Changelog published — changelog is documented on the docs site at https://docs.mulesoft.com/release-notes/, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://docs.mulesoft.com/general/llms.txt (1 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Code samples in docs — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — A full-corpus llms-full.txt is published at https://docs.mulesoft.com/general/llms-full.txt, so agents can ingest all your docs in one fetch. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (mulesoft/docs-general, 600 snippets). Investigated: docs 100%, sdk 83%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 226 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — Read/write classification is partial: 27/27 classified (26 read, 1 write). Investigated: sdk 100%, spec 80%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 3 assessed pages (3 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.
- [skip] Agent-navigable, token-efficient docs — 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

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Pagination documented & consistent — The 4 list endpoint(s) expose no pagination parameters, forcing an agent into all-or-nothing reads. Investigated: spec 75%, docs 75%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 50%.
- [warn] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 15%, docs 15%.

## Executive Summary

MuleSoft's API program shows strong API design and discoverability foundations, but two areas create meaningful friction for partners and their AI agents: documentation pages lack structured metadata that answer engines need to surface and cite your APIs, and code samples are absent across sampled docs pages, forcing partners to hand-write every integration from scratch. Closing these two gaps — machine-readable doc signals and ready-to-use code examples — will materially shorten the path from discovery to a partner's first successful call.