# Rezolve — API Agent Score

> Score: 64/100 (Grade: C) | Domain: rezolve.com | Rubric: 1.0.0 | Checked: July 29, 2026

Rezolve scored 64/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 68/100 (C)
- Agent Discovery: 69/100 (C)
- Agent Understanding: 78/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — info.version="0.2.2" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — 92% of operations have documented schemas (target 95%+). Investigated: spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — Code samples present on 8/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%, spec 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://docs.rezolve.ai/docs/getting-started/introduction; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 8/20 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://docs.rezolve.ai/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Description completeness — 42% description completeness. Investigated: spec 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%, sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 4 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 50 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://docs.rezolve.ai/llms.txt, https://docs.rezolve.ai/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap present (965 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 1 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, spec 50%.
- [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 sampled pages support .md URLs (0/50 tested). Investigated: docs 71%.
- [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 9 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 2 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 1 server entries; no test-key prefixes 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

Rezolve's API program shows genuine strengths in API design and documentation reachability, but partners and their agents face two critical blockers: the integration surface is unreliable for automated workflows (no idempotency guidance, rate-limit signaling, or pagination conventions) and the onboarding experience is too thin to support self-serve adoption. Fixing operational reliability and safe integration must come first — these gaps directly prevent partners from building production-grade integrations. Alongside that, shoring up description quality, changelog discipline, and agent-readable context will unlock the speed and confidence that turn a first call into a live integration.