Skip to Content
Overview

agent-runner

agent-runner is a multi-tenant SaaS platform that proxies Anthropic Claude API calls to Amazon Bedrock. A company signs up as a tenant, invites its developers, issues grants and API keys, and points Claude Code (or any Anthropic-compatible client) at a per-tenant HTTPS endpoint. Usage is metered and billed through Stripe.

Set ANTHROPIC_BASE_URL=https://<slug>.proxy.<domain>/anthropic/v1 in Claude Code and every Claude API call flows through agent-runner instead of going straight to Anthropic — adding centralized governance, per-developer attribution, quota enforcement, and metered billing on top of Bedrock.

What it does

The platform ships one shared control plane in front of several data-plane products:

  • Claude Model Proxy — an Anthropic-Messages-API-compatible gateway to Amazon Bedrock, fronted by a wildcard CloudFront distribution at a per-tenant URL. Streams Bedrock’s SSE response byte-for-byte and meters every request.
  • Control plane — Cognito-authenticated REST API for tenants, users, grants, keys, the model catalog, and billing.
  • Skills platform — deploy and schedule Python functions (built with the Claude Agent SDK) on Amazon Bedrock AgentCore Runtime.
  • MCP gateway & hosting — a managed AgentCore Gateway per tenant that exposes external APIs and upstream MCP servers to any MCP-compatible client.
  • agent-runner-auth — a Go CLI that bridges Claude Code’s apiKeyHelper to the platform’s Cognito OAuth (PKCE) stack.

Where to start

Features

Roles at a glance

  • Tenant Owner — creates the tenant, invites developers, manages grants, keys, billing, and settings. One owner per tenant (the first user).
  • Developer — invokes the proxy within their grant, views their own usage, and creates their own API keys.
  • Service Account — a non-human identity (CI pipeline, scheduled job, Claude Desktop) that authenticates with an ar_live_... key. Not a Cognito user.
  • Platform Admin (copebit) — internal operator who manages the model catalog, approves new tenants, and monitors all tenants.

Phase status

The proxy and control plane (Phase 0) are the implemented MVP. The skills platform and MCP hosting extend it. See the Architecture section for the deployed system as it stands today.

Last updated on