Gateway

A unified gateway for LLM providers, MCP tool surfaces, and agent runtimes—with one identity, policy layer, and audit trail

Exemplar

How this harness capability fits the Exemplar platform—governed agent operations, not a standalone prompt playground.

Why Exemplar

Fragmented integrations mean every agent team rebuilds bridges to AWS, Linear, Snyk, and internal APIs—with different auth and no shared audit.

Exemplar’s gateway is the standardized bridge: one governed tool surface whether the caller is a human in the console or an agent in an IDE.

What Exemplar delivers

Out-of-the-box MCP and API integrations anchored to catalog, incidents, and Day 2 Ops actions.

LLM routing with policy hooks—model choice, fallbacks, and spend caps at the gateway—not buried in client config.

How teams use it

Connect MCP clients to Exemplar; agents inherit the same integrations and RBAC as console users.

Register custom agents and sub-agents; orchestration routes tool calls through the gateway with structured allow/deny responses.

Capability checklist

Route LLM traffic through governed endpoints
Expose platform capabilities as MCP tools (Cursor, Claude, custom agents)
Same tool surface for console operators and autonomous agents
Scoped credentials—secrets never enter model context

Developer guide

Official documentation on docs.exemplar.dev for this capability.

Open developer guide (opens in a new tab)

Contact sales

Harness Platform is scoped per deployment. Talk to us about this feature.

From the blog

Related posts on exemplar.dev.