Higgsfield API vs Magic Hour MCP

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.

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.

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.

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.

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.

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.