Overview

The ModernLoop Internal Broker API is an OpenAPI-first HTTP layer that re-exposes internal service integrations (Linear, GitHub, Slack, Datadog, Sentry, and more) as REST endpoints behind a single API key. It replaces direct MCP tool access with a spec-driven surface that also powers generated connectors (TypeScript SDK, MCP server, and CLI).

Base URL

All service routes live under /rest/v1/<service>/.... For example, Linear's provider-native GraphQL API is available at POST /rest/v1/linear/graphql.

Versioning

• API version: v1 is encoded in every service path (/rest/v1/...). Breaking changes will ship under a new path prefix.
• OpenAPI document version: the info.version field in openapi/openapi.json tracks the broker release.
• Interactive reference: the broker also serves Scalar at GET /rest/v1/reference and the raw spec at GET /rest/v1/openapi.json (both unauthenticated).

What this site covers

• Guides (this section) explain auth, read vs write semantics, and connectors.
• API Reference is generated from openapi/openapi.json at build time. When a new service is added to the spec, its operations appear here automatically. No manual docs edits are required.

Health check

GET /health returns { "status": "ok" } and does not require authentication. Use it for load balancer and deployment probes.

Next steps

• Authentication: how to call protected endpoints.
• MCP: connect an MCP client to the production Streamable HTTP endpoint.
• Read vs write operations: which endpoints mutate upstream state.
• API Reference: the full operation list grouped by service.

For the complete guide set, visit the ModernLoop API documentation.