# Video editing API integration checklist

Source guide: https://valmera.io/video-editing-api
Prepared: September 6, 2026

Use this blank checklist on your own representative media. It is a proposed evaluation, not a completed test, certification or performance benchmark. Record actual observations and unresolved items before selecting a provider.

## Workload and delivery

- [ ] Name the provider, plan, interface and documentation version reviewed.
- [ ] Define the source formats, typical duration and largest expected upload.
- [ ] Specify the required output: preview, final MP4, subtitle file or editable project.
- [ ] Record whether human review or a separate export step is part of delivery.
- [ ] Define what counts as an accepted video: content, captions, sound, crop and runtime.

## Connection and discovery

- [ ] Confirm account eligibility and supported authorization before submitting media.
- [ ] Initialize the client using the supported transport and protocol version.
- [ ] Inspect current schemas; follow catalog pagination when supplied.
- [ ] Keep secrets and signed media URLs out of shared logs and evaluation notes.
- [ ] Record returned project and asset identifiers, not guessed values.

## First representative operation

- [ ] Verify that the source upload and any required analysis have completed.
- [ ] Select the intended project and edit version.
- [ ] Identify whether each timestamp is source time or edited output time.
- [ ] Submit one bounded operation using its actual schema.
- [ ] Record the tool/render result and any returned job identifier.
- [ ] Observe that same job to a terminal result; separate a wait timeout from job failure.
- [ ] Inspect the rendered media and its relevant project state.

## Recovery

- [ ] Establish what the provider guarantees about retries and duplicate requests.
- [ ] Reconcile unknown outcomes before resubmitting a mutation.
- [ ] Check supported authorization recovery, malformed-request errors and missing assets.
- [ ] If webhooks are supported, check verification, delivery, retry and reconciliation rules.
- [ ] Confirm that the consumer can retrieve media for the full queue and processing duration.

## Cost and acceptance

- [ ] Count attempts, revisions and accepted outputs separately.
- [ ] Record source analysis, rendering, model, storage, transfer and review costs.
- [ ] Inspect the complete downloaded file, including any intro or branded ending.
- [ ] Check the next system's codec, dimensions, audio, storage and runtime requirements.
- [ ] Record unresolved delivery or access constraints before expanding the workload.

## Valmera-specific checks

The public contract checked September 6, 2026 exposes MCP editing and preview review. Final-export creation remains in Studio. Check the actual session and https://valmera.io/mcp/tools for current availability.

- [ ] Main video meets both the 14 GB and three-hour limits.
- [ ] Account access and metering are confirmed for the intended MCP workflow.
- [ ] Each child clip project has its own editing, review and delivery plan.
- [ ] Studio final creation is included in the workflow; retrieving a link is a separate action.
- [ ] Burned-in captions and the lack of Studio SRT/VTT or NLE project/XML/AAF handoff fit the requirement.

## Record the result

Provider and plan:

Media sample and expected delivery:

Connection and operation observations:

Failure/recovery observations:

Attempts, accepted outputs and measured usage:

Remaining constraints:

Decision and reason: