VeloRix Tournaments Developer & Agent Resources

Every machine-readable resource VeloRix Tournaments publishes, so AI agents and developers can integrate with the VeloRix esports tournament platform without scraping the app shell. A markdown version of this page is at /md/developers.md.

VeloRix MCP server (Model Context Protocol)

VeloRix publishes a first-party MCP server over Streamable HTTP with public, read-only tools. Start from the handshake document at /.well-known/mcp, which carries the endpoint URL, transport and tool list. That URL is also a live handshake: POST a JSON-RPC 2.0 initialize request to /.well-known/mcp (or to /mcp) and VeloRix answers over Streamable HTTP; GET returns the manifest.

• Transport: Streamable HTTP (JSON-RPC 2.0)
• Authentication: none — public read-only tools
• Server: velorix-mcp (title "VeloRix", version 0.1.0)

Tools

• list_published_pages — list published VeloRix pages (tournaments, announcements, policies).
• get_page — full markdown of one published page by slug.
• get_active_apk — active Android APK version, changelog, size and download path.
• get_site_status — live or maintenance state plus the current status message.

Public JSON API (OpenAPI 3.1)

VeloRix Tournaments publishes a read-only REST API described by an OpenAPI 3.1 document at /openapi.json (mirrored at /api/openapi.json). Base URL https://velorix-esports.tech/api/v1. No authentication is required. Errors use application/problem+json with an error object carrying code, message and hint so agents can recover without parsing HTML.

• getApiIndex — GET /api/v1 — API metadata and operation list.
• listPages — GET /api/v1/pages — published VeloRix pages.
• getPage — GET /api/v1/pages/{slug} — full markdown of one page.
• getActiveApk — GET /api/v1/apk/active — active Android release.
• getSiteStatus — GET /api/v1/status — live or maintenance status.

VeloRix API rate limits

The VeloRix Tournaments API allows 120 requests per 60 second window per client IP, with no key or account. Every response carries RateLimit-Policy: "default";q=120;w=60 and RateLimit: "default";r=<remaining>;t=<reset seconds> (RFC 9331), mirrored by X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. On 429 VeloRix returns Retry-After plus the rate_limited error code; agents should self-throttle from RateLimit rather than retrying blindly.

VeloRix API error model (RFC 9457)

Every non-2xx response is application/problem+json with type, title, status, detail, instance and a machine-readable error object (code, message, hint). Stable codes: bad_request, page_not_found, no_active_release, endpoint_not_found, method_not_allowed, rate_limited, upstream_error, backend_unavailable, internal_error. Every operation in the OpenAPI document references this schema for its 4xx, 5xx and default responses.

VeloRix API versioning & deprecation policy

The API is versioned in the URL path (/api/v1) and every response carries X-API-Version. Breaking changes ship only as a new path version; a deprecated version sends Deprecation (RFC 9745) and Sunset (RFC 8594) headers for at least 180 days before removal, and every response links the policy with Link; rel="deprecation-policy". Full policy: /md/versioning.md. Machine-readable API catalog (RFC 9727 linkset): /.well-known/api-catalog. This page is also served at /docs and /api-docs.

Agent files

• /llms.txt — curated site index including a "when to use VeloRix" section
• /llms-full.txt — full text of all VeloRix editorial guides
• /ai.txt — training, retrieval and attribution policy
• /robots.txt — crawler rules; AI crawlers explicitly allowed
• /sitemap.xml — all public URLs

Markdown content negotiation

Send Accept: text/markdown to /, /about, /contact, /privacy, /terms, /download or /developers and VeloRix responds with text/markdown plus Vary: Accept, Accept-Encoding. The same documents are directly addressable under /md/, for example /md/index.md. Appending ?format=md forces the markdown variant.

Conventions

• Unknown paths return a real HTTP 404 with a short markdown body linking these resources.
• Public content may be quoted with attribution to "VeloRix Tournaments" and a link to the source page.
• Private areas (/vx-control, /crew) are excluded from crawling.