For AI agents: the complete documentation index is at https://docs.routebase.dev/llms.txt. Every page is also available as Markdown by appending index.md to its URL or by sending Accept: text/markdown.
Team & Settings

Integrations

Routebase connects to the rest of your toolchain in a few ways. There are event-driven webhooks, formatted alerts in Slack and Microsoft Teams, API keys for programmatic access, and the MCP interface for AI agents. This guide gives you the map. Webhooks along with Slack and Teams alerts sit in the Notifications group of the settings sidebar, and API keys sit in Security.

Webhooks — push events to your tools

Webhooks are the most flexible integration point. Routebase sends an HTTP POST to your endpoint whenever selected events occur in your organization, so you can wire events into your CI/CD pipeline, Slack, or any other external service. They're managed on Settings → Webhooks. See Webhooks for event types, payloads, and delivery.

Messaging — alerts in Slack and Teams

For chat channels there is a dedicated surface. Settings → Messaging connects Slack in one click or Microsoft Teams, and it posts formatted alerts for contract drift, incidents and test failures instead of raw JSON. See Messaging.

API keys — pull data and automate

API keys authenticate scripts, CI jobs, and other machine clients against the Routebase API at api.routebase.dev, with scoped permissions and optional project restrictions. They're managed on Settings → API Keys. See API Keys.

AI agents — connect via MCP

Routebase speaks the Model Context Protocol (MCP), so AI agents and assistants can read and work with your API workspace directly. See the MCP Quickstart to connect an agent, and MCP Authentication for how agents authenticate.

  • Webhooks — HTTP POST notifications for organization events
  • Messaging — formatted alerts in Slack and Microsoft Teams
  • API Keys — programmatic access to the Routebase API
  • Notification Defaults — org-wide defaults for in-app and email notifications