Developers

Runbear developer resources

Runbear exposes two programmable surfaces — a REST API and an MCP server — plus a set of index files written for agents. Everything below lives at a fixed URL and is safe to fetch without a browser.

Runbear REST API

Base URL https://api.runbear.io/v1. Authenticate with an organization API key as Authorization: Bearer <key>. Each key carries a scope: the capabilities it holds (chat, manageAgents, manageApiKeys) and an optional allowlist of agents it may touch. The specification publishes the permission every operation requires, so an integration can request only the access it needs.

  • OpenAPI 3.1 specificationEvery operation with a unique operationId, a description, typed parameters and response schemas, and the API-key scope it requires under x-runbear-scope.
  • Runbear API referenceThe same specification, rendered and browsable.
  • Web SDKEmbed a Runbear agent in your own product.
  • Traces APIRead execution traces for an agent's runs.

Runbear MCP server

Streamable HTTP endpoint at https://api.runbear.io/mcp. Add it to an MCP client with claude mcp add --transport http runbear https://api.runbear.io/mcp, or fetch runbear.io/mcp with Accept: application/json to get the same configuration as a pasteable mcpServers object.

Agent-readable files

Any page on runbear.io also answers with markdown instead of HTML when the request advertises Accept: text/markdown.