# Razorpay — API Agent Score

> Score: 71/100 (Grade: B) | Domain: razorpay.com | Rubric: 1.0.0 | Checked: July 24, 2026

Razorpay scored 71/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 93/100 (A+)
- Developer Experience: 51/100 (D)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 57/100 (D)
- Agent Usability: 78/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 8 of 92 public signatures use loose types (anyTypeRatio=0.087). Investigated: sdk 93%, spec 50%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" 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 0%.
- [pass] Example coverage — 100% example coverage across params + responses. Investigated: spec 100%, sdk 100%.

### Developer Experience

- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Description completeness — 144/168 operations carry a description. Investigated: sdk 86%, spec 0%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/razorpay, 1205 snippets). Investigated: docs 100%, sdk 100%, cli 100%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 50 failed to fetch. Investigated: docs 71%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [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 — Could not fetch HTML for any pages to compare; 50 failed to fetch. Investigated: docs 65%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, sdk) is 1% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination params detected on 27 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server (https://dashboard.dev.razorpay.in) declared in spec with distinguishable test credentials. Investigated: spec 100%, docs 100%, sdk 50%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.

## Executive Summary

Razorpay's API program stands out for its strong, machine-readable contract and solid agent discovery foundations — but partners are hitting two critical walls: there is no self-service portal or quickstart to get them to a first successful call, and the API's error responses and agent context files are not structured in ways that AI agents can parse and act on. Fixing self-service onboarding and machine-readable agent context should be the immediate priority, as these gaps are the most likely to stall partner programs and block agentic integrations before they begin.