Developer Guide
For developers who want to build on Rival directly, this is the map. Everything here is covered in depth on its own page; this guide orients you to the pieces and the order they fit together.
Build a tool
Section titled “Build a tool”A tool packages executable logic into a reusable, versioned endpoint. Start with Creating a tool for the end-to-end flow, or let RivalBot generate a first draft from a plain-language description.
Choose a runtime
Section titled “Choose a runtime”Tools can be written in Python, JavaScript, Lua, or Storm. See Writing Code for the runtimes and when to use each.
Expose capabilities over MCP
Section titled “Expose capabilities over MCP”To make a capability usable by any agent through a standard protocol, build it as an MCP server. See What is MCP.
Version and publish
Section titled “Version and publish”Tools use immutable semantic versions, and publishing for others follows your organization’s governance. See Versions & Publishing and What is a tool.
In the enterprise
Section titled “In the enterprise”Whether a developer’s tools need approval before others can use them, and which models and connectors they can reach, is set by role and policy. See Roles & Permissions and Governance & Approvals.