Developer Resources & API

Official machine-readable specifications, API interfaces, Model Context Protocol (MCP) servers, and content negotiation instructions for the Rewa Division Cricket Association (RDCA) archive.

1. Model Context Protocol (MCP) Server

We support the Model Context Protocol (MCP) for native AI agent integration (Claude, ChatGPT, LangChain, AutoGPT). Agents can connect directly to our MCP live handshake endpoint:

• Live Handshake Endpoint: https://rewa-cricket-division.vercel.app/.well-known/mcp
• MCP Manifest: https://rewa-cricket-division.vercel.app/.well-known/mcp/manifest.json
• Transport: Streamable HTTP & JSON-RPC 2.0 handshake

2. OpenAPI 3.1 Specification

The complete RESTful and static content architecture is cataloged under the OpenAPI 3.1 specification:

• OpenAPI 3.1 Document: /api/openapi.json
• Endpoints Covered: Homepage, Matches & Scorecards, Players & Stats, Teams, Tournaments, Venues, Search Index.

3. Markdown Content Negotiation (Accept: text/markdown)

Following the acceptmarkdown.com specification, our edge infrastructure provides proactive content negotiation for all archive resources:

curl -s -H "Accept: text/markdown" https://rewa-cricket-division.vercel.app/players/pranav-dwivedi/

Every response returns Content-Type: text/markdown; charset=utf-8 accompanied by Vary: Accept, Accept-Encoding. Layout headers, navigation drawers, and decorative markup are removed, and scorecards are rendered as clean GitHub-flavored markdown pipe tables.

4. Machine-Readable Knowledge Indexes

• /llms.txt — Curated site summary, best-fit use cases, and route index.
• /llms-full.txt — Complete documentation and match catalog in plain text.
• /agent-instructions.txt — Query recipes and tool definitions.
• /search-index.json — Full-text index of all pages for offline indexing.
• /sitemap.xml — Canonical sitemap containing verified URLs.