Stripe vs Razorpay for AI agents
Stripe is more ready for AI agents than Razorpay: 87 vs 82 out of 100. Stripe is ahead on semantic HTML, image alt text and a sign-up page agents can open. Razorpay is ahead on an OpenAPI spec and SoftwareApplication data.
What an agent finds
| Stripe | Razorpay | |
|---|---|---|
| Score | 87/100 | 82/100 |
| Blocks AI agents | No | No |
| robots.txt disallows | No AI bots | Bytespider |
| llms.txt | At the root | At the root |
| Remote MCP server | mcp.stripe.com/ | mcp.razorpay.com/mcp |
| Docs MCP server | none found | razorpay.com/docs/mcp |
| OpenAPI spec | none found | razorpay.com/openapi.json |
| Developer docs | docs.stripe.com/development | razorpay.com/docs/home.md |
| Public pricing | stripe.com/de/pricing | razorpay.com/pricing.md |
| Self-serve sign-up | Yes, opens for agents | No self-serve page we could open |
Check by check
60 core points every site needs, plus 40 split between letting an agent sign a team up and connecting through the API. Sign-up and API checks count half each.
| Check | Points | Stripe | Razorpay |
|---|---|---|---|
| Core | 58 | 51 | |
| Agents get the real page, not a bot wall | 12 | ✓ | ✓ |
| robots.txt lets user-triggered agents in | 6 | ✓ | ✓ |
| Answer-engine crawlers are allowed | 4 | ✓ | ✓ |
| Content is in the raw HTML | 6 | ✓ | ✓ |
| Semantic HTML (main, nav, header) | 4 | ✓ | · |
| Icon buttons and links have names | 3 | ✓ | ✓ |
| Form fields have labels | 3 | ✓ | ✓ |
| Images have alt text | 3 | ✓ | · |
| The page has an H1 | 2 | ✓ | ✓ |
| Structured data (JSON-LD) | 5 | ✓ | ✓ |
| Meta description and Open Graph tags | 3 | ✓ | ✓ |
| sitemap.xml | 3 | ✓ | ✓ |
| llms.txt | 4 | ✓ | ✓ |
| Dates show the content is fresh | 2 | · | · |
| Sign-up | 15 | 12 | |
| Public pricing page | 5 | ✓ | ✓ |
| A self-serve sign-up link | 4 | ✓ | ✓ |
| Sign-up page opens for agents | 3 | ✓ | · |
| A free plan or trial | 3 | ✓ | · |
| No card needed to start | 2 | · | · |
| SoftwareApplication data | 3 | · | ✓ |
| API | 13.5 | 18.5 | |
| OpenAPI spec | 3.5 | · | ✓ |
| Remote MCP server | 4 | ✓ | ✓ |
| Docs as markdown | 2.5 | ✓ | ✓ |
| Self-serve API keys | 3 | · | ✓ |
| OAuth client self-registration | 2.5 | ✓ | ✓ |
| OAuth discovery metadata | 1.5 | ✓ | ✓ |
| SDKs and a CLI | 1.5 | ✓ | ✓ |
| Free tier or test keys | 1.5 | ✓ | · |
Automated, read-only scan of each homepage, robots.txt, llms.txt, docs, OpenAPI paths and MCP endpoints on 3 Nov 2026. How scoring works.
Check them again today
Sites change. Run the live scan for the current result, or check your own site.
Questions
Is Stripe or Razorpay better for AI agents?
Stripe is more ready for AI agents than Razorpay: 87 vs 82 out of 100. Stripe is ahead on semantic HTML, image alt text and a sign-up page agents can open. Razorpay is ahead on an OpenAPI spec and SoftwareApplication data. Scores are from our scan on 3 Nov 2026.
Does Stripe have an MCP server?
Yes. Our scan reached a remote MCP server at https://mcp.stripe.com/ on 3 Nov 2026.
Does Razorpay have an MCP server?
Yes. Our scan reached a remote MCP server at https://mcp.razorpay.com/mcp on 3 Nov 2026.
Does Stripe block AI agents?
No. Stripe served its homepage to an AI user-agent and its robots.txt doesn't disallow any of the AI crawlers we check.
Does Razorpay block AI agents?
Not outright: its homepage loads for an AI user-agent, but its robots.txt disallows Bytespider.