Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Amagi website screenshot

Amagi

Amagi is a cloud-based technology company for the broadcast and streaming television industry. Its SaaS platform handles channel creation and playout, content distribution across linear, FAST (free ad-supported streaming TV) and connected-TV (CTV) destinations, server-side dynamic ad insertion and monetization, and viewership/ads analytics — letting content owners run live, linear and VOD channels from the cloud. Founded in 2008 and backed by Accel and Norwest Venture Partners, Amagi exposes internal operational REST APIs (Mapsor job/user orchestration and the services-amagi-tv key/customer service) documented via ReDoc, plus open-source tooling such as SLV. This profile was enriched by the API Evangelist pipeline from Amagi's published OpenAPI and public developer surface.

agent native

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Amagi the way a machine reads it — 24 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amagi scores 35.0/100 (thin), with a separate agent-readiness read of 65/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 35.0/100 · thin
Contract Quality 12.7 / 25
Developer Ergonomics 9.6 / 20
Commercial Clarity 2.1 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 65/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Amagi

Each block below is one kind of artifact we hold for Amagi. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 20

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Amagi Add User API

The Add User API from Amagi — 1 operation(s) for add user.

Amagi Cancel API

The Cancel API from Amagi — 1 operation(s) for cancel.

Amagi Create Customer API

The Create Customer API from Amagi — 1 operation(s) for create customer.

Amagi Delete Customer API

The Delete Customer API from Amagi — 1 operation(s) for delete customer.

Amagi Destroy API

The Destroy API from Amagi — 1 operation(s) for destroy.

Amagi Disable User API

The Disable User API from Amagi — 1 operation(s) for disable user.

Amagi Enable User API

The Enable User API from Amagi — 1 operation(s) for enable user.

Amagi Get Info API

The Get Info API from Amagi — 1 operation(s) for get info.

Amagi Get Key API

The Get Key API from Amagi — 1 operation(s) for get key.

Amagi Get Metrics API

The Get Metrics API from Amagi — 1 operation(s) for get metrics.

Amagi Head Key API

The Head Key API from Amagi — 1 operation(s) for head key.

Amagi List API

The List API from Amagi — 1 operation(s) for list.

Amagi List Keys API

The List Keys API from Amagi — 1 operation(s) for list keys.

Amagi List Versions API

The List Versions API from Amagi — 1 operation(s) for list versions.

Amagi Logs API

The Logs API from Amagi — 1 operation(s) for logs.

Amagi Regenerate Token API

The Regenerate Token API from Amagi — 1 operation(s) for regenerate token.

Amagi Retry API

The Retry API from Amagi — 1 operation(s) for retry.

Amagi Set Key API

The Set Key API from Amagi — 1 operation(s) for set key.

Amagi Status API

The Status API from Amagi — 1 operation(s) for status.

Amagi Submit API

The Submit API from Amagi — 1 operation(s) for submit.

Scroll within the panel for all 20 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

amagi-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Amagi Authentication

apiKey · 3 schemes

SECURITY

Amagi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Amagi Agentic Access

20 operations · 8 acting · 1 human-in-the-loop

20 operations · 8 acting

AGENTIC

Resources

Every other property we hold for Amagi — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/amagi · machine-readable index on apis.io