iZotope
iZotope is a Cambridge, Massachusetts audio software company founded in 2001 that builds professional plugins for music production, audio repair, mixing, and mastering, with deep investments in AI-assisted and machine-learning-driven audio processing. Its flagship products include RX (audio restoration and dialogue repair widely used in film, TV, and podcast post-production), Ozone (mastering suite with Master Assistant), Neutron (mixing suite with Mix Assistant and Track Assistant), Nectar (vocal processing with Vocal Assistant), Tonal Balance Control (cross-session referencing), and the Music Production Suite bundle. iZotope's assistive technologies analyze incoming audio and propose starting-point chains, EQ curves, dynamics settings, and spectral repairs — historically among the first widely adopted AI features in the professional audio plugin market. iZotope announced on 2 July 2026 that it is joining Boris FX, leaving the Native Instruments / Soundwide group it had belonged to since 2024; it now sits in the Boris FX Pro Audio division alongside Sound Forge, Acid Pro, Sequoia, Samplitude and CrumplePop. Product distribution is via desktop plugin formats (VST3, AudioUnit, AAX) for DAWs such as Pro Tools, Logic, Ableton Live, Cubase, Studio One, and Reaper. iZotope publishes no OpenAPI and runs no developer platform for its DSP or machine-learning audio algorithms — those are licensed to OEM partners as contract-gated embedded SDKs. What it does operate is a real, publicly reachable AGENT COMMERCE surface on its own domain: an anonymous Model Context Protocol endpoint at https://www.izotope.com/api/ucp/mcp implementing the Universal Commerce Protocol (UCP 2026-04-08) with 13 catalog, cart, checkout and order tools carrying real JSON Schema 2020-12 input contracts, discoverable through /llms.txt, /agents.md and /.well-known/ucp, with OAuth 2.0 / OpenID Connect customer accounts at account.izotope.com. The commerce API is the storefront for the software, not a product in its own right.
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 iZotope the way a machine reads it — 9 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 — iZotope scores 27.9/100 (thin), with a separate agent-readiness read of 35/100 (agent ready). 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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from iZotope'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/izotope/"
title="iZotope on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/izotope.svg"
alt="iZotope Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/izotope/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/izotope/"
title="iZotope on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/izotope/card.svg"
alt="iZotope 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 iZotope
Each block below is one kind of artifact we hold for iZotope. 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 2
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.
iZotope Commerce Agent API (UCP / MCP)
iZotope's agent-facing commerce API — an anonymous JSON-RPC 2.0 Model Context Protocol endpoint served on iZotope's own host implementing the Universal Commerce Protocol 2026-04...
iZotope Storefront Product JSON
The read-only storefront endpoints iZotope documents for agents in its own llms.txt — product and collection JSON, product pages by handle, search, and the sitemap. No authentic...
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.
iZotope MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Izotope Rate Limits
RATE LIMITSSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 iZotope — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/izotope · machine-readable index on apis.io
This is an independent, third-party profile of iZotope, 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.