PrismClip

API and MCP integrations

Connect PrismClip to an AI-assisted video workflow.

PrismClip provides OAuth-connected MCP, owner-scoped API keys, durable jobs, and a published OpenAPI contract. Public operations upload local media, import Google Drive and YouTube sources, inspect owned projects, queue automatic clip suggestions, and read job state.

Add PrismClip to an MCP client →Browse the API
01

Owner-scoped access

MCP clients connect through PrismClip OAuth. REST integrations can create a named API key with only the scopes the workflow needs.

02

Shared contracts

REST validation, OpenAPI operations, and MCP tools derive from the same Zod schemas and operation registry.

03

Durable work

Long-running operations return job IDs. Stable idempotency keys make uncertain requests safe to retry.

MCP connection

Add PrismClip with one command.

Your MCP client discovers PrismClip OAuth from the server URL and opens a browser for authorization. The same URL can be added to clients such as Claude and ChatGPT that support remote Streamable HTTP MCP servers.

codex mcp add prismclip --url https://prismclip.com/mcp

REST and headless authentication

Create a scoped API key from your account.

Send the key in the Authorization header as a Bearer token. API keys support REST automation and manually managed MCP clients. Keep keys in a secret manager and use the narrowest scopes the workflow needs.

Authorization: Bearer $PRISMCLIP_API_KEY

REST quick start

Queue suggestions for an analyzed project.

Use a project owned by the key’s account after full visual analysis completes. Reuse the same idempotency key when retrying this exact request, then poll the returned job URL.

curl https://prismclip.com/api/v1/projects/PROJECT_ID/auto-pick \
  --request POST \
  --header "Authorization: Bearer $PRISMCLIP_API_KEY" \
  --header "Idempotency-Key: workflow-2026-07-15-001" \
	  --header "Content-Type: application/json" \
	  --data '{"count": 6}'

Remote sources

Queue an authorized Google Drive file or a best-effort YouTube import.

Google Drive accepts one explicit file URL. Public files are read directly, and private files use the account connection created through PrismClip’s Google OAuth flow. YouTube imports depend on current provider access and restrictions. Both operations return a durable import job for polling and cancellation.

curl https://prismclip.com/api/v1/imports/google-drive \
  --request POST \
  --header "Authorization: Bearer $PRISMCLIP_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"url":"https://drive.google.com/file/d/FILE_ID/view"}'

curl https://prismclip.com/api/v1/imports/IMPORT_JOB_ID \
  --header "Authorization: Bearer $PRISMCLIP_API_KEY"

Workflow boundary

Use the product and integration surfaces together.

  1. 1
    Ingest and analyze

    Upload locally when possible. Google Drive is the preferred remote source. YouTube import is best-effort.

  2. 2
    Queue and inspect

    Use REST or MCP to request suggestions from completed visual evidence and poll durable job state.

  3. 3
    Review and render

    Open the owned project in Studio to curate passages, choose framing and captions, and render clips.

  4. 4
    Submit for review

    Eligible clips enter the existing human moderation workflow. Public integrations do not receive moderation authority.

Shared knowledge

Guidance published to developers and MCP clients.

These versioned guides are the same sources returned by the MCP server under stable prismclip://guides/ URIs.

PrismClip workflow

Use PrismClip as the durable video-processing layer in an AI-assisted workflow. Work with projects owned by the API-key principal. Wait for asynchronous jobs to reach a terminal state before starting dependent work. Use transcript or visual evidence to create complete moments, render those moments, and keep a person responsible for review and publication decisions.

The Studio and Library remain complete interfaces for the same projects. API and MCP operations add integration access; they do not transfer ownership or moderation authority.

Choose a source

Use a direct local-file upload when the source file is available to the user or calling workflow. It is the most reliable ingestion path.

Use Google Drive for a remote source when the PrismClip account has explicitly authorized access to the file. Google Drive is the preferred remote path for a durable cloud copy.

Treat YouTube import as best-effort. Availability, download permission, restrictions, and provider behavior can prevent ingestion. Surface provider failures to the user and avoid repeatedly submitting the same unavailable source.

Retain the original source until ingestion completes. Check known size and duration limits before starting work.

Evidence and moments

Use transcript evidence for spoken answers, arguments, explanations, jokes, and stories. Use visual evidence for actions or scenes that are not adequately described by speech. Use mixed evidence when both the words and visible event define the moment.

Keep source ranges inside the cited evidence. Prefer complete exchanges, actions, and thoughts over arbitrary duration slices. Preserve evidence references so a person can review each selection in context.

Jobs and idempotency

Long-running PrismClip operations return durable job IDs. Poll at a modest interval and stop when the job reaches a terminal state. Do not create dependent work while a prerequisite job remains queued or running.

Use one stable Idempotency-Key for retries of the same intended operation. Use a new key when the intended input changes. A replay can return the original job instead of creating duplicate work.

Rendering and review

Choose aspect ratio, framing, captions, and source ranges deliberately. Review the opening frame, ending boundary, crop behavior, caption accuracy, and source context before using a completed clip.

Feed submission sends an eligible render into PrismClip's normal review system. Public API keys and MCP tools never approve, reject, withdraw, or publish feed submissions.

Errors and recovery

Correct validation and ownership errors before retrying. Respect Retry-After on rate limits. For provider failures, preserve the reported category and let the user choose another source path when access or availability is the cause.

Reuse the same idempotency key after transport interruption or an uncertain response. Create a new key only for a changed request. Include PrismClip request and job IDs in support reports without including API keys or source credentials.

Inspect every live operation.

The API reference is generated from the production contract and includes scopes, request fields, responses, errors, and MCP mappings.

Open API reference →