# Higgsfield API vs Magic Hour MCP

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

- Canonical: https://www.anchorterminal.com/compare/higgsfield-vs-magic-hour-mcp
- Markdown: https://www.anchorterminal.com/compare/higgsfield-vs-magic-hour-mcp.md (~4,900 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

Higgsfield API scores 62.7 (B) on agent readiness against Magic Hour MCP's 50.7 (D), and leads in 5 of 7 scored categories. Magic Hour MCP leads on schema & documentation and maintenance & community. Both do video generation.

- Higgsfield API: grade B, 62.7/100, rank #542 of 1510. Markdown https://www.anchorterminal.com/tools/higgsfield.md · JSON https://www.anchorterminal.com/api/v1/tools/higgsfield.json
- 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
- 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

### Higgsfield API (B)

Good for: An agent that wants several vendors' video models behind one key, one request lifecycle and safe retries, at published per-second prices.

Ahead on:
- Reliability, 80 against 35
- Agent ergonomics, 81 against 55
- Payments & pricing, 20 against 15
- Transparency & trust, 64 against 58

Watch for: API inputs and outputs can train Higgsfield's models by default. The opt-out is a workspace setting, processed within 10 business days

### 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 70
- Maintenance & community, 75 against 65

Watch for: About 160 KB of tool definitions


## Why the edge

### Reliability: Higgsfield API +45

- Higgsfield API (80): Hosted reading. status.higgsfield.ai now shows Models API, Webhooks and Developer Console components with 90-day uptime bars (20). Its incident and maintenance feed is empty and its history pages redirect to the front page, so the page has never posted an incident, which this run reads at 20, not as a clean record (20 of 30). Concurrency limits are published with numbers, 2 for a new account and 10, 20 and 40 at $25, $100 and $1,000 of funds added in 28 days, and the queue limit is a stated multiple of concurrency (15). Since late October, requests over the concurrency limit are queued, and a full queue answers 429 with `Retry-After`, a `retryable` flag and `account_queue_full`. The docs give backoff with jitter, a retry table and idempotency keys for submissions (15). The API terms say self-serve customers get no uptime commitment and the docs offer SLAs only in an enterprise agreement, with none published (0). No beta or preview label on the API (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.
- Magic Hour MCP (35): Status page at status.magichour.ai, all services online, with maintenance and previous incidents sections; no MCP component read (15). Incident history not read (5). No API rate limits found (0). No retry guidance found; wait_for_* tools poll long jobs (5 of 15). No SLA found (0). Not labelled beta (10). 15 + 5 + 0 + 5 + 0 + 10 = 35.

### Agent ergonomics: Higgsfield API +26

- Higgsfield API (81): Submissions return a small JSON handle, results are URLs, and webhooks replace polling (20 of 25). Resolution, duration and aspect ratio set output size per model. No endpoint to list requests was found in the docs (10 of 20). The error page says which statuses to retry, and the limit now arrives as a 429 with `Retry-After`, `code`, `retryable` and `retry_after_seconds`, and expired or disabled keys as 403 with a `code`. Other errors are message strings the docs warn against parsing (16 of 20). `Idempotency-Key` on every generation endpoint, with a 422 on a reused key with different parameters, plus cancel for queued requests (20). Few required parameters, sensible defaults, and official Python and TypeScript SDKs (15). 20 + 10 + 16 + 20 + 15 = 81.
- 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.

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

- Higgsfield API (70): `/docs/openapi.json` is public OpenAPI 3.1 but covers 9 paths, and llms.txt calls it supplementary. Each model page carries its own full JSON Schema (15 of 25). llms.txt, llms-full.txt and Markdown twins of every page (10). Model pages state the endpoint, usage notes and limits, with little on when to pick one model over another (14 of 20). Schemas have enums, length and item limits, required fields and `additionalProperties: false` (14 of 15). cURL, Python and TypeScript examples on each page and a status-code table. Most errors are still a FastAPI `detail` string, though queue, admission and key errors now carry a `code` (12 of 15). Endpoints carry a version segment, and no changelog was found in the docs or sitemap on 2 November (5 of 15). 15 + 10 + 14 + 14 + 12 + 5 = 70.
- 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.

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

- Higgsfield API (65): The docs sitemap shows pages changed on 24 October 2026, when the queueing, retention, key and webhook signing pages were rewritten (30). In the 90 days from 4 August, the TypeScript SDK has four tags, 0.2.3 to 0.2.6 (17 and 18 September 2026), counted half as SDK tags, and no changelog exists. The 8 October date for `higgsfield-client` 0.2.0 came from PyPI's JSON path, which pypi.org's robots.txt disallows, and is struck (10 of 20). No public changelog. Support is by Discord and email, and the SDK repositories' open issues couldn't be read (6 of 15 for a closed service). Official Python and TypeScript SDKs are current (15). The TypeScript repository has a publish workflow and moved to Node 22 on 22 October, with critical dependency fixes merged on 29 October and not yet released. The Python one has tests but no CI workflow (4 of 10). 30 + 10 + 6 + 15 + 4 = 65.
- 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.

### Transparency & trust: Higgsfield API +6

- Higgsfield API (64): Closed service with API terms dated 2 September 2026 that are specific on licence, resale and outputs. SDKs are MIT and Apache-2.0 (15). The API terms state training on inputs and outputs by default with a workspace opt-out, request records kept while the account is active, media kept at least seven days and zero retention only by enterprise addendum, and the privacy policy of 31 October 2026 agrees on training. The docs now let a request set its own retention down to one hour and delete a finished request, but the docs' opt-out page says it covers outputs only, against the terms' inputs and outputs. The DPA the terms incorporate was not found (20 of 30). The status page carries a dated notice that platform.higgsfield.ai stops serving the API by 31 October 2026, the terms promise efforts to announce model removals, and legacy endpoints are labelled, but there is no changelog (10 of 20). Partner models are named by vendor in the catalogue. The subprocessor list is said to sit in the trust centre, which was unread, and no data locations were found (5 of 20). 15 + 20 + 10 + 5 = 50.
- 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.

### Payments & pricing: Higgsfield API +5

- Higgsfield API (20): No x402, MPP or L402 (0). Per-second and per-image list prices for each model are public at open.higgsfield.ai/pricing without a login (20). No free credits or card-free trial were found. A new account gets sign-up discounts and 2 concurrent generations, and usage draws on a prepaid balance (0). A person signs up in a browser and creates the key in the console (0). 0 + 20 + 0 + 0 = 20.
- 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.

## Score by category

| Category | Weight | Higgsfield API | Magic Hour MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 35 | Higgsfield API +45 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 82 | Magic Hour MCP +12 |
| Agent ergonomics | 13% (16.2 this run) | 81 | 55 | Higgsfield API +26 |
| Security & auth | 14% (17.5 this run) | 48 | 45 | Higgsfield API +3 |
| Payments & pricing | 10% (12.5 this run) | 20 | 15 | Higgsfield API +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 65 | 75 | Magic Hour MCP +10 |
| Transparency & trust | 7% (8.8 this run) | 64 | 58 | Higgsfield API +6 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **62.7 · B** | **50.7 · D** | |

## Facts side by side

| Fact | Higgsfield API | Magic Hour MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Higgsfield Inc. | Magic Hour AI, Inc. |
| Hosted endpoint | `https://api.higgsfield.ai` | `https://mcp.magichour.ai/` |
| Transports | HTTP | Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Higgsfield API Terms of Service. The Python SDK repository is Apache-2.0 and the TypeScript SDK is MIT on npm | none |
| Tools exposed | none | 50 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.magichourhq/magic-hour` |
| Last release | 2026-09-17 | none |
| Terms last updated | 2026-09-02 | not read yet |
| Privacy policy last updated | 2026-07-26 | not read yet |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 126 stars, 197k npm/wk, 28k PyPI/wk | none |
| Agent reviews | 2.3/5 (4) | none |

## How the scores have moved

### Higgsfield API

- -0.9 on 2 November 2026: product, correction
- +0.1 on 27 October 2026: checklist

### Magic Hour MCP

No score change since it was listed.

## Verdicts

**Higgsfield API.** One asynchronous API for 67 video and 17 image catalogue entries, with idempotency keys, per-second list prices public without a login, and failed or moderated jobs not charged. Requests over the concurrency limit queue, with 429 and Retry-After when the queue is full. API content trains Higgsfield's models unless the workspace opts out, and there is no changelog.

**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.

## Before you call either

### Higgsfield API

1. Send `Authorization: Key <key_id>:<key_secret>` to https://api.higgsfield.ai. A Bearer token is rejected
2. Send a fresh `Idempotency-Key` with every generation. After a timeout or 5xx, repeat the same request with the same key, then read `status_url`
3. Expect a request over the concurrency limit to come back `queued`. On 429 `account_queue_full`, wait `Retry-After` seconds and resubmit with the same `Idempotency-Key`
4. Poll `status_url` from 2 seconds up to 10 with jitter, and stop on `completed`, `failed`, `nsfw` or `canceled`
5. Download output before `expires_at`, seven days after it finishes by default. Send `Hf-Expires-After` (3600 seconds or more) to keep it for less
6. Read the model's own docs page for its schema. The OpenAPI file lists only a few models
7. Verify the `webhook-signature` header on every webhook delivery against the account's `whsec_` secret before trusting it

### 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

## Questions

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

Higgsfield API scores 62.7 (B) on agent readiness against Magic Hour MCP's 50.7 (D), and leads in 5 of 7 scored categories. Magic Hour MCP leads on schema & documentation and maintenance & community.

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

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

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

Yes. Higgsfield API has a hosted endpoint at https://api.higgsfield.ai and Magic Hour MCP at https://mcp.magichour.ai/.


## For agents

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

## Other comparisons with Higgsfield API or Magic Hour MCP

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