---
title: "Waymark report for razorpay.com"
canonical: "https://waymark.genedai.me/score/razorpay.com"
last-updated: "2026-08-26T16:28:48.185Z"
---

# Waymark report for razorpay.com

Waymark scored razorpay.com 84.1/100 (B) on 26 Aug 2026.
Score: 84.1/100 — Usable with gaps
Scanned: 2026-08-26T16:28:48.185Z
Canonical report: https://waymark.genedai.me/score/razorpay.com

## Layer breakdown

- Discovery: 18.7/20 (19 of 21 eligible checks passed)
- Access: 23.2/30 (28 of 42 eligible checks passed)
- Usability: 33.8/40 (20 of 27 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. OpenAPI / Swagger link

- Layer: access
- Result: failed
- Evidence: No OpenAPI/Swagger link in HTML.
- Recommended fix: Link to an OpenAPI or Swagger document from the homepage.

### 2. RSS or Atom feed

- Layer: access
- Result: failed
- Evidence: No RSS/Atom link.
- Recommended fix: Expose an RSS or Atom feed for machine subscribers.

### 3. CORS / API hint

- Layer: access
- Result: partial
- Evidence: No CORS header or obvious API path.
- Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients.

### 4. Login or docs link

- Layer: access
- Result: failed
- Evidence: No login/docs/developers link.
- Recommended fix: Link to login and developer documentation from the homepage.

### 5. AI crawlers not blanket-blocked

- Layer: access
- Result: failed
- Evidence: robots.txt Disallow: / for * or common AI bots.
- Recommended fix: Avoid Disallow: / for GPTBot, ClaudeBot, PerplexityBot unless intentional.

### 6. MCP SSE / HTTP hint

- Layer: usability
- Result: failed
- Evidence: No MCP/SSE hint on the homepage.
- Recommended fix: Document an MCP HTTP or SSE endpoint.

### 7. Webhook or API docs

- Layer: usability
- Result: failed
- Evidence: No webhook/API docs mention.
- Recommended fix: Document webhooks and REST/RPC APIs for agents.

### 8. Trust pages

- Layer: access
- Result: failed
- Evidence: No about/privacy/contact link.
- Recommended fix: Link about or privacy from the homepage.

### 9. Sitemap lastmod

- Layer: discovery
- Result: failed
- Evidence: Sitemap without lastmod.
- Recommended fix: Add lastmod dates to sitemap entries.

### 10. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching razorpay.com.
- Recommended fix: Publish an official package whose homepage is this domain.

### 11. Content without JavaScript

- Layer: access
- Result: partial
- Evidence: Raw HTML has 300659 characters but no H1.
- Recommended fix: Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

### 12. Agent instruction / when-to-use

- Layer: access
- Result: failed
- Evidence: Agent file exists without when-to-use guidance.
- Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.

### 13. Organization schema completeness

- Layer: access
- Result: failed
- Evidence: Organization JSON-LD missing address.
- Recommended fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress).

### 14. llms.txt links resolve

- Layer: access
- Result: partial
- Evidence: 7 real, 1 homepage-shell, 0 dead of 8 sampled links.
- Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200.

### 15. Markdown frontmatter metadata

- Layer: access
- Result: failed
- Evidence: Served markdown has no YAML frontmatter block.
- Recommended fix: Open served markdown with a --- frontmatter block carrying title plus description, canonical, or last-updated.

### 16. Markdown content negotiation (acceptmarkdown.com)

- Layer: access
- Result: failed
- Evidence: Markdown negotiation response lacks Vary: Accept.
- Recommended fix: On responses that serve text/markdown via Accept negotiation, add Accept to the Vary header.

### 17. Page token budget

- Layer: access
- Result: failed
- Evidence: Extracted text is 300659 characters, over the ~100k agent budget.
- Recommended fix: Keep each page's extracted text under ~100K characters so it fits an agent's context window.

### 18. Accessible document structure

- Layer: usability
- Result: failed
- Evidence: Homepage HTML lacks main/nav/H1 document structure.
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

### 19. REST pagination pattern

- Layer: usability
- Result: failed
- Evidence: List endpoints lack a documented pagination shape.
- Recommended fix: Use a consistent pagination shape on list endpoints and define the fields in OpenAPI.

### 20. Multi-language SDK packages

- Layer: usability
- Result: failed
- Evidence: No npm+PyPI official packages whose homepage is this domain.
- Recommended fix: Publish official SDK packages on npm and PyPI whose homepage is this domain.

### 21. auth.md structure

- Layer: usability
- Result: failed
- Evidence: auth.md exists but is missing the WorkOS-style sections (3 hits).
- Recommended fix: Structure /auth.md with Discover, Register, Claim, Use, Errors, and Revocation (WorkOS auth.md).

### 22. Agent auth WWW-Authenticate hint

- Layer: usability
- Result: failed
- Evidence: MCP 401 without resource_metadata (WWW-Authenticate: missing).
- Recommended fix: Return 401 with WWW-Authenticate: Bearer resource_metadata= on a documented API entry point.

### 23. Agent-UA markdown docs

- Layer: access
- Result: failed
- Evidence: Docs host did not serve markdown to GPTBot (HTTP 200, text/html; charset=utf-8).
- Recommended fix: Serve text/markdown to GPTBot (and similar agent UAs) on your docs host.

## Interpretation

Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan.

The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.