Before connecting a video API to ComfyUI
Check model IDs, node provenance, request parameters, billing and platform requirements before preparing an API workflow.
This is a preparation checklist. We have not tested a platform-specific ComfyUI node or published a working workflow. An available API does not establish ComfyUI compatibility. No top-up or paid API request is needed to follow this guide.
1. Identify the model and platform
Open a model in our directory and record the platform, exact platform model ID, API mode and source check date. Similar display names do not guarantee that model identifiers are interchangeable.
Filter platform rates by mode, resolution, currency and billing unit. Per-second, per-request and per-million-token rates remain separate. When pricing is unverified, check the platform source.
2. Check node provenance
Look for integration documentation published or explicitly linked by the platform. Record the node repository, maintainer, supported platforms and models, version or commit, dependencies and license. Review third-party nodes independently.
We have not verified specific node compatibility for the video models in this directory. We therefore do not provide untested node installation commands or workflow downloads.
3. Match the API and node parameters
| Check | What to establish |
|---|---|
| Authentication | Required authentication and how the node reads credentials |
| Model | Exact platform ID and supported model version |
| Input | Text-to-video or image-to-video; image formats and upload method |
| Output | Duration, resolution, aspect ratio and audio options |
| Task result | Submission, task-status checks and result retrieval |
| Billing | Charges for submission, failure, cancellation and retries |
Keep real API credentials out of shared workflows, screenshots, logs and tutorials. Inspect exported files before sharing them.
4. Verify access and payment requirements
Check supported regions, registration requirements, payment methods and minimum top-up using official sources. Website access, API documentation and account-level access are separate checks. Also review refunds, balance expiry, rate limits and concurrency.
An “Unverified” field on our site does not mean there are no restrictions or that your region is supported.
5. Keep evidence when testing later
Before any paid test, establish a spending cap and failure-billing rules. Record environment and node versions, platform, model ID, parameters, date, task ID, result and actual bill without publishing credentials.
If task status is unclear, inspect the original task before submitting another request. A platform and node combination should only be labelled tested after obtaining reproducible evidence.
Read next: Reading API prices · Estimating request costs