# WSO2 — API Agent Score

> Score: 59/100 (Grade: D) | Domain: wso2.com | Rubric: 1.0.0 | Checked: July 31, 2026

WSO2 scored 59/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 60/100 (C)
- Agent Discovery: 72/100 (B)
- Agent Understanding: 54/100 (D)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 89/89 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [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] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://apim.docs.wso2.com/en/latest/tutorials/scenarios/scenario4-user-signup-approval-flow/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 77 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 37/65 operations lack a description. Investigated: sdk 43%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (wso2/docs-apim, 8781 snippets). Investigated: docs 100%, sdk 100%, cli 50%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 30%, sdk 0%.
- [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] 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 1 assessed pages (1 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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [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.

## Executive Summary

WSO2's API program shows strength in discovery infrastructure and schema quality, but two areas are putting partner outcomes at risk: agent understanding is critically underdeveloped (no machine-readable instructions, no structured data for AI indexing), and agent usability is failing on runnable truth and operational reliability documentation. Prioritize giving partners and their agents the executable context and clear operational contracts they need to integrate with confidence — without requiring a support conversation.