# Redis — API Agent Score

> Score: 86/100 (Grade: A) | Domain: redis.io | Rubric: 1.0.0 | Checked: July 24, 2026

Redis scored 86/100 (A), classified "ai-ready".

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

## Summary

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

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 89/100 (A)
- Agent Discovery: 78/100 (B)
- Agent Understanding: 79/100 (B)
- Agent Usability: 90/100 (A+)

## Check Results

### API Design

- [pass] Schema coverage & depth — 57/57 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="Version 1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.
- [pass] Example coverage — Code samples in 4 language(s) across docs (top: shell, python, javascript); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%, spec 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://redis.io/try-free/; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 4 language(s) across docs (top: shell, python, javascript); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Description completeness — 90% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog documented in the docs site at https://redis.io/docs/latest/develop/tools/insight/release-notes/index.html. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (4 variants scanned starting at https://redis.io/docs/latest/getting-started/) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (redis/docs, 38181 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] Docs reachable, not hard auth-gated — 5 JavaScript redirect(s) detected across 50 sampled pages. Investigated: docs 63%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 50%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 11 distinct 4xx/5xx response codes documented. Investigated: spec 100%, docs 100%, sdk 100%.
- [pass] Operation purpose clarity — 99% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 12 of 44 pages have substantive content differences between markdown and HTML (avg 18% missing). Investigated: docs 40%.
- [pass] Docs structured data — JSON-LD Article markup on 8/12 assessed pages (67%) with dateModified present (3 JS-rendered). Investigated: docs 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [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%.
- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://redis.io/tutorials/rate-limiting-in-dotnet-with-redis/. Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — sandbox documented in the docs site at https://redis.io/tutorials/howtos/redis-sandbox/. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Redis's API program shows strong fundamentals in design, onboarding, and documentation reachability — partners can find and evaluate the APIs with relative ease. The two areas that most limit partner and agent success today are the absence of agent-readable context (no AGENTS.md instruction file for AI coding tools) and the lack of a runnable, test-backed collection (meaning agents and partners must guess at real request/response shapes and integration patterns). Closing these two gaps should be the immediate priority to ensure AI-assisted integrations are accurate, fast, and trustworthy.