# SAS — API Agent Score

> Score: 65/100 (Grade: C) | Domain: sas.com | Rubric: 1.0.0 | Checked: July 30, 2026

SAS scored 65/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 79/100 (B)
- Developer Experience: 59/100 (D)
- Agent Discovery: 68/100 (C)
- Agent Understanding: 71/100 (B)
- Agent Usability: 51/100 (D)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — OpenAPI 3.0.3 declared (3.0.x; 3.1 adds JSON Schema 2020-12 alignment but is not required for full credit). Investigated: spec 100%, docs 100%.
- [pass] Schema coverage & depth — 14/14 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 48% example coverage. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Code samples in docs — Code samples present on 2/18 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 86% description completeness (target 90%+). Investigated: spec 100%, sdk 50%.
- [pass] Changelog published — Newest official SDK activity 13 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [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%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/support_sas_en, 170 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/18 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap present (365 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.sas.com/llms.txt, https://developer.sas.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 9 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%, sdk 0%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/18 tested). Investigated: docs 42%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 9% (threshold 35% for full credit).
- [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%.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 2 list endpoint(s). Investigated: docs 100%, spec 75%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [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%.

## Executive Summary

SAS's API program shows strengths in core API design and documentation parseability, but two areas demand immediate attention: agent discoverability and partner usability. There is no machine-readable discovery layer (no llms.txt, no agent instructions file, no structured docs data), meaning AI agents cannot find or reason about SAS APIs without human intervention. At the same time, the absence of a self-service portal, runnable collections, and operational reliability signals (idempotency, rate-limit handling) means partners cannot get hands-on or build with confidence. Prioritizing a discoverable, executable front door — with agent-ready context layered on top — will unlock self-serve partner onboarding and make SAS APIs viable for AI-driven integrations.