# Render — API Agent Score

> Score: 75/100 (Grade: B) | Domain: onrender.com | Rubric: 1.0.0 | Checked: July 30, 2026

Render scored 75/100 (B), classified "partially-ready".

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

## Summary

- Overall: 75/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 84/100 (A)
- Developer Experience: 66/100 (C)
- Agent Discovery: 92/100 (A+)
- Agent Understanding: 79/100 (B)
- Agent Usability: 58/100 (D)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="1.0.0") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 76% 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 50%.
- [fail] Example coverage — 4% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://dashboard.render.com/register; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 89% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — changelog documented in the docs site at https://render.com/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [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] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/mql5docs_onrender, 18801 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 81%.
- [warn] Crawlable / AEO — Sitemap present (3 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 11 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 98% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 2 of 50 pages have substantive content differences between markdown and HTML (avg 2% missing). Investigated: docs 75%.
- [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 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

- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://api-docs.render.com/reference/rate-limiting. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — Pagination params detected on 59 list endpoint(s). Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. 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

Onrender's API discovery foundation is strong, with crawlability and documentation discoverability in excellent shape — partners and agents can find the API without friction. However, the program has critical gaps in three areas that will stall partner adoption: agents and AI coding tools lack the runnable, grounded context they need to integrate correctly; partners have no fast, self-serve path to a first working call; and the API contract itself is missing the examples and idempotency signals that make safe, confident integration possible. Prioritizing executable context, onboarding acceleration, and agent-readiness will unlock real partner momentum.