Skip to main content
Managed Agents on Synth are exposed through a backend BFF path that mirrors Anthropic-compatible semantics for core agent/session workflows.

​
Path model

Use this mapping when reasoning about requests:
LayerPath family
Client-facing (Synth backend)/api/managed-agents/anthropic/v1/*
Upstream in horizons-private/anthropic/v1/*
Anthropic public style reference/v1/*

​
Current scope

This surface is intentionally limited right now:
  • Anthropic-compatible view only (no native managed-agents /v1 surface via backend in this phase)
  • Phase 1 allowlist for high-traffic operations (health, environments, agents, sessions, events, streams)

​
Auth and headers

  • Backend edge auth: Authorization: Bearer <SYNTH_API_KEY>
  • Compatibility headers:
    • anthropic-version
    • anthropic-beta (for managed-agents features)
Backend forwards only the allowed compatibility headers and keeps org context at the edge.

​
Streaming

SSE endpoints are part of the supported Phase 1 contract:
  • GET /api/managed-agents/anthropic/v1/sessions/{session_id}/stream
  • GET /api/managed-agents/anthropic/v1/sessions/{session_id}/events/stream
See the reference page for endpoint-by-endpoint coverage and examples.

Anthropic-compatible API Reference

Endpoint coverage, example requests, and Phase 1 operation list.

Auth + Headers

Required auth, compatibility headers, and forwarding policy.

Streaming (SSE)

Stream endpoint usage, required headers, and reconnect guidance.

synth-ai Usage

Use client.managed_agents correctly alongside pools/containers clients.

Paths + Contracts

Mapping table, pinned OpenAPI, allowlist, and CI contract checks.