# Magic Hour MCP vs PixVerse API

> Magic Hour MCP scores 50.7 (D) to PixVerse's 42.5 (E) for video generation. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pixverse
- Markdown: https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pixverse.md (~4,100 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Magic Hour MCP scores 50.7 (D) on agent readiness against PixVerse API's 42.5 (E), and leads in 5 of 7 scored categories. PixVerse API leads on agent ergonomics. Both do video generation.

- Magic Hour MCP: grade D, 50.7/100, rank #1053 of 1510. Markdown https://www.anchorterminal.com/tools/magic-hour-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/magic-hour-mcp.json
- PixVerse API: grade E, 42.5/100, rank #1279 of 1510. Markdown https://www.anchorterminal.com/tools/pixverse.md · JSON https://www.anchorterminal.com/api/v1/tools/pixverse.json
- Best video generation for AI agents: https://www.anchorterminal.com/best/video-generation/index.md
- All 183 video comparisons: https://www.anchorterminal.com/compare/video-generation/index.md

## Which one, for what

### Magic Hour MCP (D)

Good for: Agents making short-form video and images, from talking photos and ads to lip-synced translations, on a credit plan.

Ahead on:
- Schema & documentation, 82 against 58
- Security & auth, 45 against 28
- Payments & pricing, 15 against 10
- Maintenance & community, 75 against 52
- Transparency & trust, 58 against 46

Watch for: About 160 KB of tool definitions

### PixVerse API (E)

Good for: Agents doing many short edits (restyle, swap, lip sync, sound effects) on a budget.

Ahead on:
- Agent ergonomics, 70 against 55

Also in its favour:
- Runs on your own machine

Watch for: Plan prices and the dollar value of a credit sit on a JavaScript-only billing page


## Why the edge

### Schema & documentation: Magic Hour MCP +24

- Magic Hour MCP (82): All 50 tools read from tools/list with JSON Schema inputs and 29 enums, built from Magic Hour's OpenAPI specification (25). llms.txt (10). Long descriptions with a get_workflow_guide tool for choosing between them (17 of 20). Typed inputs with enums and no free-form objects (15). Worked examples; error responses not documented (5 of 15). Dated changelog with entries on 3 to 5 November 2026 (10 of 15, product changelog rather than MCP versions). 25 + 10 + 17 + 15 + 5 + 10 = 82.
- PixVerse API (58): No OpenAPI file published (0). llms.txt on the platform docs (10). Each endpoint page says what the operation does, and the model tables say which models support it. Older model tables still sit beside current ones (12). Typed parameters with fixed values for model, quality, duration and aspect ratio (11). Examples on each endpoint. Results use numeric status codes (1 done, 5 generating, 7 moderation failure, 8 failed) that an agent has to look up (10). A dated changelog that adds models and endpoints every few weeks (15).

### Maintenance & community: Magic Hour MCP +23

- Magic Hour MCP (75): Changelog entries on 3, 4 and 5 November 2026 (30). More than three dated entries in 90 days (20). Changelog and support; issues on the public MCP repository not read (10 of 25). Registry entry io.github.magichourhq/magic-hour (0.1.1, 4 November) (15). No package health read (0). 30 + 20 + 10 + 15 + 0 = 75. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
- PixVerse API (52): Model reading. The changelog's latest entry is the One-click VibeMV API on 24 September 2026, with five dated entries since July, after C1 on 7 April (30). Legacy models from V3.5 to V5.6 stay callable, and no removals were found (10). Dated changelog and support through the platform (12). No official SDK. The stdio MCP package hasn't been released since October 2025 (0). Nothing current to assess for package health (0).

### Security & auth: Magic Hour MCP +17

- Magic Hour MCP (45): API keys as Bearer tokens or OAuth through the Claude and ChatGPT connectors (20 of 30). Destructive deletes are annotated; no read-only key (8 of 20). Tools return generated media, not third-party text (10). No audit log found (0). No security.txt or certifications found; face and voice tools come with policy limits in the terms (7 of 20). 20 + 8 + 10 + 0 + 7 = 45.
- PixVerse API (28): Model reading of the checklist (credential, training, retention, operator visibility, programme). One API key in an API-KEY header (20). The platform terms don't say whether inputs or outputs train models (0). No retention period or deletion call found (0). A usage deduction query API since 18 August 2026 shows what each job cost, no audit log (8). No security.txt, bug bounty or certification found (0).

### Agent ergonomics: PixVerse API +15

- Magic Hour MCP (55): 50 tools totalling about 160 KB of definitions (5). list_saved_items and project getters; limited size controls (10 of 20). Error handling not documented (5 of 20). Every tool annotated, 14 read-only and the three deletes marked destructive (20). Few required inputs and SDKs (Python, Node and others listed in the docs) (15). 5 + 10 + 5 + 20 + 15 = 55.
- PixVerse API (70): Small JSON responses with a video id, plus webhooks so an agent needn't poll (25). Duration, quality and aspect ratio set output size. No task list endpoint found (10). Numeric status and error codes are documented but cryptic (12). Every submit needs a fresh UUID in Ai-trace-id, and reusing one returns the earlier job instead of creating a new one. That works as an idempotency key, though an agent that reuses an id by mistake gets the old video back (20). Required trace header, no official SDK. A CLI and an MCP server exist (3).

### Transparency & trust: Magic Hour MCP +12

- Magic Hour MCP (58): Closed service under terms naming Magic Hour AI, Inc., revised 3 October 2026 (15). The privacy policy says prompts, uploads and outputs aren't sold or used to train models, for free and paid accounts, and MCP requests are handled the same way; retention periods aren't given (20 of 30). No deprecation policy found (5 of 20). Subprocessors not read (10 of 20, model providers named in tool docs). 15 + 20 + 5 + 10 = 50.
- PixVerse API (46): Closed models under platform terms (updated 4 September 2026) with MOTIVAI PRIVATE LIMITED, with AIVORA PTE. LTD. named as an affiliate. The terms give API users the rights in generated video and allow commercial use (15). The terms don't address training on inputs or outputs and give no retention period, only that data may be deleted when service ends. We didn't read the privacy policy against them (5). No deprecation policy, but legacy models are labelled (5). No subprocessor list or data locations found (0).

### Payments & pricing: Magic Hour MCP +5

- Magic Hour MCP (15): No machine payment protocol (0). Plan and credit-pack prices public, per-tool credit costs not read (10). 400 sign-up credits with no card, but API access sits on paid plans (5 of 20). A person signs up for a key in a browser (0). Tool discovery is open, but calls need a key (0). 0 + 10 + 5 + 0 = 15.
- PixVerse API (10): No x402, MPP or L402 (0). Credits per second are public for every model, and the docs peg $1 at five 5 second V6 720p clips, but plan prices sit on a billing page that needs JavaScript, so the dollar price of a credit isn't stated outright (10). A Free API plan with 3 concurrent jobs is listed, but the docs don't say whether it includes credits (0). A person signs up on the platform (0).

## Score by category

| Category | Weight | Magic Hour MCP | PixVerse API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 35 | 35 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 82 | 58 | Magic Hour MCP +24 |
| Agent ergonomics | 13% (16.2 this run) | 55 | 70 | PixVerse API +15 |
| Security & auth | 14% (17.5 this run) | 45 | 28 | Magic Hour MCP +17 |
| Payments & pricing | 10% (12.5 this run) | 15 | 10 | Magic Hour MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 75 | 52 | Magic Hour MCP +23 |
| Transparency & trust | 7% (8.8 this run) | 58 | 46 | Magic Hour MCP +12 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **50.7 · D** | **42.5 · E** | |

## Facts side by side

| Fact | Magic Hour MCP | PixVerse API |
| --- | --- | --- |
| Kind | MCP server | Model API |
| Vendor | Magic Hour AI, Inc. | PixVerse |
| Hosted endpoint | `https://mcp.magichour.ai/` | `https://app-api.pixverse.ai/openapi/v2` |
| Transports | Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Tools exposed | 50 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.magichourhq/magic-hour` | not listed |
| Last release | none | 2026-09-24 |
| Terms last updated | not read yet | 2026-09-04 |
| Privacy policy last updated | not read yet | 2026-05-07 |
| Customer content may train models | not read yet | yes, with an opt-out |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### Magic Hour MCP

No score change since it was listed.

### PixVerse API

- -0.1 on 29 October 2026: new evidence
- +0.2 on 27 October 2026: checklist
- -0.4 on 8 October 2026: checklist

## Verdicts

**Magic Hour MCP.** Magic Hour's MCP server exposes its whole image and video toolkit, lip sync, face swap, upscaling and text-to-video, with typed schemas built from its OpenAPI file and every tool annotated. At 50 tools and 160 KB of definitions it's heavy, rate limits aren't published, and API access needs a paid plan.

**PixVerse API.** V6 at about $0.04 a second at 720p, with audio and clips up to 15 seconds. Plan prices and the dollar value of a credit sit on a JavaScript-only billing page.

## Before you call either

### Magic Hour MCP

1. Call get_workflow_guide first to pick the right tool
2. Use the wait_for_* tools instead of polling project status yourself
3. Check credits with get_account_info before long video jobs
4. Only swap faces or voices of people who consented

### PixVerse API

1. Generate a new UUID for Ai-trace-id on every new submit. Reuse it only to fetch the same job again
2. Poll the result endpoint. Status 1 is done, 5 generating, 7 moderation failure, 8 failed
3. Moderate prompts before calling. Repeated status 7 results can suspend the key
4. Use model v6 or c1 for new work. Older model tables still sit in the docs

## Questions

### Which is better for AI agents, Magic Hour MCP or PixVerse API?

Magic Hour MCP scores 50.7 (D) on agent readiness against PixVerse API's 42.5 (E), and leads in 5 of 7 scored categories. PixVerse API leads on agent ergonomics.

### Do Magic Hour MCP and PixVerse API need an API key?

Magic Hour MCP takes an API key or an OAuth sign-in. PixVerse API needs an API key.

### Can an agent call Magic Hour MCP and PixVerse API without installing anything?

Yes. Magic Hour MCP has a hosted endpoint at https://mcp.magichour.ai/ and PixVerse API at https://app-api.pixverse.ai/openapi/v2.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pixverse.json, and with the fewest tokens: https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pixverse.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "magic-hour-mcp", "b": "pixverse"}`. From a terminal: `anchor compare magic-hour-mcp pixverse`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/magic-hour-mcp.json and https://www.anchorterminal.com/api/v1/tools/pixverse.json

## Other comparisons with Magic Hour MCP or PixVerse API

- [Alibaba Wan (Model Studio) vs Magic Hour MCP](https://www.anchorterminal.com/compare/alibaba-wan-vs-magic-hour-mcp.md)
- [Alibaba Wan (Model Studio) vs PixVerse API](https://www.anchorterminal.com/compare/alibaba-wan-vs-pixverse.md)
- [fal video models vs Magic Hour MCP](https://www.anchorterminal.com/compare/fal-video-vs-magic-hour-mcp.md)
- [fal video models vs PixVerse API](https://www.anchorterminal.com/compare/fal-video-vs-pixverse.md)
- [framefields vs Magic Hour MCP](https://www.anchorterminal.com/compare/framefields-vs-magic-hour-mcp.md)
- [framefields vs PixVerse API](https://www.anchorterminal.com/compare/framefields-vs-pixverse.md)
- [Google Veo vs Magic Hour MCP](https://www.anchorterminal.com/compare/google-veo-vs-magic-hour-mcp.md)
- [Google Veo vs PixVerse API](https://www.anchorterminal.com/compare/google-veo-vs-pixverse.md)
- [Higgsfield API vs Magic Hour MCP](https://www.anchorterminal.com/compare/higgsfield-vs-magic-hour-mcp.md)
- [Higgsfield API vs PixVerse API](https://www.anchorterminal.com/compare/higgsfield-vs-pixverse.md)
- [HyperFrames vs Magic Hour MCP](https://www.anchorterminal.com/compare/hyperframes-vs-magic-hour-mcp.md)
- [HyperFrames vs PixVerse API](https://www.anchorterminal.com/compare/hyperframes-vs-pixverse.md)
- [Kling AI API vs Magic Hour MCP](https://www.anchorterminal.com/compare/kling-vs-magic-hour-mcp.md)
- [Kling AI API vs PixVerse API](https://www.anchorterminal.com/compare/kling-vs-pixverse.md)
- [Luma AI API vs Magic Hour MCP](https://www.anchorterminal.com/compare/luma-vs-magic-hour-mcp.md)
- [Luma AI API vs PixVerse API](https://www.anchorterminal.com/compare/luma-vs-pixverse.md)
- [Magic Hour MCP vs MiniMax Video API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-minimax-video.md)
- [Magic Hour MCP vs OpenAI Sora API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-openai-sora.md)
- [Magic Hour MCP vs Pika API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-pika.md)
- [Magic Hour MCP vs Popcraft MCP](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-popcraft-mcp.md)
- [Magic Hour MCP vs Replicate video models](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-replicate-video.md)
- [Magic Hour MCP vs Runway API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-runway.md)
- [Magic Hour MCP vs Seedance on BytePlus ModelArk](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-seedance-on-byteplus-modelark.md)
- [Magic Hour MCP vs Vidu API](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-vidu.md)
- [MiniMax Video API vs PixVerse API](https://www.anchorterminal.com/compare/minimax-video-vs-pixverse.md)
- [OpenAI Sora API vs PixVerse API](https://www.anchorterminal.com/compare/openai-sora-vs-pixverse.md)
- [Pika API vs PixVerse API](https://www.anchorterminal.com/compare/pika-vs-pixverse.md)
- [PixVerse API vs Popcraft MCP](https://www.anchorterminal.com/compare/pixverse-vs-popcraft-mcp.md)
- [PixVerse API vs Replicate video models](https://www.anchorterminal.com/compare/pixverse-vs-replicate-video.md)
- [PixVerse API vs Runway API](https://www.anchorterminal.com/compare/pixverse-vs-runway.md)
- [PixVerse API vs Seedance on BytePlus ModelArk](https://www.anchorterminal.com/compare/pixverse-vs-seedance-on-byteplus-modelark.md)
- [PixVerse API vs Vidu API](https://www.anchorterminal.com/compare/pixverse-vs-vidu.md)
- [Clueso vs Magic Hour MCP](https://www.anchorterminal.com/compare/clueso-video-vs-magic-hour-mcp.md)
- [Clueso vs PixVerse API](https://www.anchorterminal.com/compare/clueso-video-vs-pixverse.md)
- [Magic Hour MCP vs sync. labs MCP server](https://www.anchorterminal.com/compare/magic-hour-mcp-vs-sync-labs-mcp.md)
- [PixVerse API vs sync. labs MCP server](https://www.anchorterminal.com/compare/pixverse-vs-sync-labs-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp