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.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Amagi the way a machine reads it — 44 machine-readable artifacts across 2 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 29.5/100 (thin), with a separate agent-readiness read of 28/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Amagi's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amagi/"
title="Amagi on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amagi.svg"
alt="Amagi Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/amagi/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amagi/"
title="Amagi on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amagi/card.svg"
alt="Amagi Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 ·
Open Collections 21
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONservices-amagi-tv Add User API
OPEN COLLECTIONservices-amagi-tv Add User Cancel API
OPEN COLLECTIONservices-amagi-tv Add User Create Customer API
OPEN COLLECTIONservices-amagi-tv Add User Delete Customer API
OPEN COLLECTIONservices-amagi-tv Add User Destroy API
OPEN COLLECTIONservices-amagi-tv Add User Disable User API
OPEN COLLECTIONservices-amagi-tv Add User Enable User API
OPEN COLLECTIONservices-amagi-tv Add User Get Info API
OPEN COLLECTIONservices-amagi-tv Add User Get Key API
OPEN COLLECTIONservices-amagi-tv Add User Get Metrics API
OPEN COLLECTIONservices-amagi-tv Add User Head Key API
OPEN COLLECTIONservices-amagi-tv Add User List API
OPEN COLLECTIONservices-amagi-tv Add User List Keys API
OPEN COLLECTIONservices-amagi-tv Add User List Versions API
OPEN COLLECTIONservices-amagi-tv Add User Logs API
OPEN COLLECTIONservices-amagi-tv Add User Regenerate Token API
OPEN COLLECTIONservices-amagi-tv Add User Retry API
OPEN COLLECTIONservices-amagi-tv Add User Set Key API
OPEN COLLECTIONservices-amagi-tv Add User Status API
OPEN COLLECTIONservices-amagi-tv Add User Submit API
OPEN COLLECTIONScroll within the panel for all 21 ·
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.
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.
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amagi · machine-readable index on apis.io
This is an independent, third-party profile of Amagi, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.