Developer & API Terms

1. Developer Plans & Subscriptions

ConfirmRoute Developer is built for software engineers, enterprise teams, and AI tool builders who require high-throughput railway data access.

2. Programmatic API and MCP Access

Authorized developers receive access to 25 specialized railway intelligence tools via our remote Model Context Protocol (MCP) server endpoint at https://www.confirmroute.com/api/mcp.

Capabilities include live train running status, 2-leg break-journey discovery, PNR confirmation prediction, 60-day availability trend calendars, coach layouts, station lookups, fare matrices, and vacant chart berth searches.

3. API Keys, Credentials and Security

API keys prefixed with cr_live_ are confidential security credentials. You must store them exclusively in environment variables or server-side secret stores.

Never embed raw API keys in client-side web applications, public Git repositories, or compiled frontend binaries. You must notify [email protected] immediately upon suspecting any key leakage.

4. Rate Limiting & Anti-Circumvention

ConfirmRoute enforces per-minute and monthly credit rate limits to ensure system stability. Exceeding limits results in HTTP 429 (Too Many Requests).

You agree not to bypass rate limits by spinning up multiple proxy accounts, rotating dummy keys, or distributing requests across unauthorized sub-networks.

5. Authorized API Usage Standards

APIs may be used only for legitimate software applications, personal workflows, and research. Unlawful surveillance, denial-of-service simulations, and bulk scraping are strictly prohibited.

6. MCP Client Configurations

When connecting ConfirmRoute MCP to IDEs and desktop clients (such as Cursor or Claude Desktop), you are responsible for securing local configuration files (claude_desktop_config.json) and restricting unauthorized local access.

7. Autonomous Agents & Loop Prevention

If deploying ConfirmRoute MCP tools within autonomous AI agents, you must implement recursion limits and guardrails to prevent infinite tool calling loops and sudden credit depletion.

8. Data Reliability & Upstream Telemetry

Data returned via API/MCP reflects dynamic Indian Railways operations. ConfirmRoute does not guarantee absolute accuracy or instantaneous synchronization of train delays or seat counts. Your application must clearly state to end users that critical travel decisions should be verified with official railway channels.

9. Caching Guidelines

Short-term caching of static data (such as station codes and route timetables) is permitted up to 24 hours. Real-time availability, live running delay, and PNR statuses must NOT be cached long-term to prevent displaying stale railway information.

10. Attribution and Branding

When displaying ConfirmRoute intelligence in third-party user interfaces, you must include a discrete attribution: 'Powered by ConfirmRoute AI'. You must never represent ConfirmRoute as an official ticketing authority.

11. Commercial Redistribution Restrictions

You may not resell or repackage raw ConfirmRoute API/MCP responses as a competing standalone API or railway proxy service without prior written enterprise authorization.

12. Security Integration Best Practices

You agree to implement industry-standard security safeguards, including HTTPS TLS 1.3 encryption, input validation, and timely key rotation.

13. Security Testing & Responsible Disclosure

Intrusive security testing, penetration testing, fuzzing, or vulnerability scans against ConfirmRoute production endpoints without prior written authorization are strictly forbidden.

Responsible vulnerability reports should be directed confidentially to [email protected].

14. Service Availability & Maintenance

We strive for 99.9% API uptime. Scheduled maintenance windows will be communicated via our developer status channels.

15. API Versioning, Changes & Deprecation

We may update tool schemas, response structures, or parameters. Breaking changes will be announced with a minimum 30-day deprecation window whenever technically feasible.

16. Quota Suspension & Enforcement

We reserve the right to suspend or revoke API credentials immediately if suspicious traffic patterns, key compromises, or terms violations are detected.

17. Billing, Monthly Credits & Top-Ups

Developer subscriptions renew monthly. Unused monthly tool credits expire at the end of each billing cycle and do not possess cash surrender value.

18. Intellectual Property of Developer Tools

ConfirmRoute retains all proprietary rights, copyright, and patent rights in all MCP servers, schemas, tool registries, and documentation.

19. Customer Application Responsibility

You retain full ownership of the custom application code and agents you construct. You are solely responsible for compliance with applicable data privacy laws regarding your application's end users.

20. Developer Support & Inquiries

For MCP integration assistance, custom enterprise rate limits, or billing inquiries, please contact our engineering support team:

Developer Support: [email protected] | Documentation: https://www.confirmroute.com/docs.