Frame.io
Frame.io is a cloud-based video review and collaboration platform, now part of Adobe, used by video and media production teams to upload media, leave frame-accurate comments, manage versions, and route work through review and approval. Its V4 developer platform exposes a REST API (base https://api.frame.io/v4) covering accounts, workspaces, projects, folders, files and uploads, comments, version stacks, shares and reviewers, collections, groups, custom actions, metadata fields, and webhooks. Authentication is OAuth2 via Adobe IMS (authorization-code for user apps and client-credentials for server-to-server), plus a Camera to Cloud (C2C) device-integration surface, an official Python SDK, the fioctl CLI, and a hosted MCP server.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Frame.io the way a machine reads it — 27 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 — Frame.io scores 55.1/100 (developing), with a separate agent-readiness read of 67/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.
How we profile Frame.io
Each block below is one kind of artifact we hold for Frame.io. 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.
Frame.io Account Permissions API
Manage Account Permissions and related operations.
Frame.io Accounts API
Manage Accounts and related operations.
Frame.io Collections API
Manage Collections and related operations.
Frame.io Comments API
Manage Comments and related operations.
Frame.io Custom Actions API
Manage Custom Actions and related operations.
Frame.io Files API
Manage Files and related operations.
Frame.io Folder Permissions API
Manage Folder Permissions and related operations.
Frame.io Folders API
Manage Folders and related operations.
Frame.io Groups API
Manage Groups and related operations.
Frame.io Metadata API
Manage Metadata and related operations.
Frame.io Metadata Fields API
Manage Metadata Fields and related operations.
Frame.io Project Permissions API
Manage Project Permissions and related operations.
Frame.io Projects API
Manage Projects and related operations.
Frame.io Search API
Manage Search and related operations.
Frame.io Shares API
Manage Shares and related operations.
Frame.io Users API
Manage Users and related operations.
Frame.io Version Stacks API
Manage Version Stacks and related operations.
Frame.io Webhooks API
Manage Webhooks and related operations.
Frame.io Workspace Permissions API
Manage Workspace Permissions and related operations.
Frame.io Workspaces API
Manage Workspaces and related operations.
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.
frameio-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Frameio Webhooks
ASYNCAPISecurity Posture 3
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 Frame.io — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
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/frameio · machine-readable index on apis.io