Integration model
- Governed tools. Systems are exposed to agents as tools over the Model Context Protocol (opens in a new tab), each agent with an explicit allow-list and nothing more.
- Model-agnostic orchestration. RUUT BRAIN routes each step to a model: open-weight models you host, or providers you approve.
- Verification on every path. RUUT FORGE screens inputs, checks tool calls against policy and validates outputs before anything executes.
- Traces by default. Every run records inputs, retrieval, tool calls, checks, approvals, latency and cost per step.
This website is agent-readable
We built ruutlabs.in the way we build agent systems: content first, machine-readable by design. Every page is server-rendered HTML, and the same content is available in formats agents prefer.
| Interface | What it gives you |
|---|---|
| /llms.txt | A curated index of the site for language models. |
| /llms-full.txt | The full site content as one plain-text document. |
/{page}.md | A clean Markdown version of any page, e.g. /platform/forge.md. |
| /.well-known/ruutlabs.json | Company facts and the product list as JSON. |
/api/mcp | A public, read-only MCP server your AI agent can query directly. |
Connect your agent to RUUT Labs over MCP
The RUUT Labs MCP server exposes read-only tools — search_site, get_product, list_solutions, get_company_facts — and one write tool, request_intro, which sends a contact request only after you confirm it. Add it to any MCP client that supports remote servers over Streamable HTTP:
{
"mcpServers": {
"ruutlabs": {
"type": "http",
"url": "https://ruutlabs.in/api/mcp"
}
}
}